-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Clearing user requests #5080
Comments
On our system.. |
Mine behaves that way also, but after using the "Check In" button it reverts back to "Check Out" and the request stays in place. I'd rather the request be removed so that the user could request it again, and the "Requested Assets" page isn't crowded with already-fulfilled requests that aren't marked that way. |
This is a good feature request - we'll try to get this into an upcoming release. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
Please don't close it, stale bot. This would still be a useful feature. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
I am still interested in this feature request. |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
As of v4.6.4, there is still no way for administrators to clear requests. I am still interested in this functionality. |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
As of v4.6.6, I still see no way for administrators to clear requests. I am still interested in this functionality. |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
I am also interested in this feature. |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
I am still interested in this feature. |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Still interested |
I'll +1 this. I manage assets for a local club and it is annoying to track down people with stale requests. |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Still intereated |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Still interested |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Still interested ! |
Very interested. Not sure why it’s not already implemented. |
If anyone is still interested, I have this feature partially implemented. You check it out @ stfloyd/snipe-it/feature/manage-requests I have this running in production at work and it does the job. I will submit a PR once I have translated the appropriate messages as right now I only have en-US and en-GB. |
Steven,
Still quite interested, is an update forthcoming on this? How long does it typically take to do these translations? Thank you for working on this, we could really use the feature.
Thanks again,
Ray
From: Steven Floyd ***@***.***>
Sent: Thursday, April 8, 2021 2:07 AM
If anyone is still interested, I have this feature partially implemented. You check it out @ stfloyd/snipe-it/feature/manage-requests<https://github.com/stfloyd/snipe-it/tree/feature/manage-requests>
I have this running in production at work and it does the job.
I will submit a PR once I have translated the appropriate messages as right now I only have en-US and en-GB.
—
You are receiving this because you commented.
Reply to this email directly,
|
Still waiting for this request to be included in an actual RELEASE build... NOT STALE |
Still interested as well |
@hrconsultJP & anyone else - sorry for the delay getting to you, I've been extremely busy with a new job and moving states (US). I have not had the time to put this all together, however most of the work is done it's just translations that need to be made. If I find time this next week or two I will see if I can pull and merge with latest and submit an official PR, but no guarantees. Thanks, |
Hello, we'd be interested in this as well. We had to resort to having our Senior IT person logging into and modifying the database directly to cancel requests, which is less than ideal and also not a sustainable solution. |
I am still interested in this. Honestly, I don't much see the usefulness of being able to request an item if an admin can't clear the request. Even after I checkout the item to the user and check it back in, it still shows as requested by the user. Basically the user has a hold on the item unless the user actually goes in and removes the request. Perhaps I am missing something? |
Do we have this implemented? Thank you! |
I'd like to see this implemented as well. I get the same results as mw-christensen. "Requests" and "checkouts" do not seem to be linked. After a requested item has been checked out, the original request for the user remains until the user cancels it. There is no UI or API call to cancel a request. |
I gave up on this a long time ago. They said it was live now, but nothing showed up. My staff has moved on and we simply stopped using the the checkout option. Not super great.
Ray Proper | GA and IT Divisions | IT Manager | How am I doing?<https://morethanrelo.com/how-are-we-doing/>
H&R Administrative Services
H&R Administrative Services is part of the H&R GROUP | www.MoreThanRelo.com<https://morethanrelo.com/>
Nagoya Office | H&R Consultants K.K.
4F Nakato Marunouchi Bldg., 3-17-6 Marunouchi, Naka-ku, Nagoya 460-0002
T +81-(0)52-973-3957 | F +81-(0)52-973-9293 | M +81-(0)70-3194-0882
Hours: 9:00 AM to 18:00 PM JST Monday through Friday.
We are ISO 27001<https://morethanrelo.com/wp-content/uploads/2018/03/genko_12284.pdf> certified. | Send me files securely<https://www16.sendthisfile.com/sendthisfile/custom.jsp?sendthisfilecode=n1rcN1pYfcBrBdNUZXOFtBV5&balance=20603>
From: Doug F. ***@***.***>
Sent: Thursday, April 13, 2023 6:07 AM
To: snipe/snipe-it ***@***.***>
Cc: ML_IT_Admin ***@***.***>; Mention ***@***.***>
Subject: Re: [snipe/snipe-it] Feature Request: Clearing user requests (#5080)
I'd like to see this implemented as well. I get the same results as mw-christensen. "Requests" and "checkouts" do not seem to be linked. After a requested item has been checked out, the original request for the user remains until the user cancels it. There is no UI or API call to cancel a request.
-
Reply to this email directly, view it on GitHub<#5080 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGLC7XLEMTC7PUN2SYIWXH3XA4KPLANCNFSM4ER62FKQ>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
It does seem a bit odd to me. I feel like it is a feature that has never worked as intended, which if this is the case I don't understand why it does not get fixed or removed. If it does work as intended then how to people actually use this feature? I honestly can't see how the request feature is useful in the state it is in. |
I'd like to also register my interest in this change. The "request" feature is unusable if the request can't be cleared in some way. |
Desired Behavior
It would be helpful to me for admins to be able to clear requests manually, or have them automatically cleared at checkout or checkin. For example:
Really any way for an admin to remove an individual request from /hardware/requested would be helpful for clearing stale requests without hunting down users.
Actual Behavior
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: