Open ghost opened 6 years ago
Also, there are no notifications when a user requests an asset. And the requested assets are not marked as fulfilled or something.
Also, there are no notifications when a user requests an asset.
Notifications do get sent out when a user requests and asset.
Sure, I have had that verified, notifications do get sent out, it was an internal issue with my SMTP. On the same note, can we have better management of requested assets?
Not limited to, but to include the following;
Thanks, that was a quick response.
I also need this feature :)
Close requested when admin checkout the items for those users :) Plus, we shouldn't have to select user field ... because it was requested from those user already.
PS :
whenever that request was reject / accept all of request need to clear up
Not sure if you mean that all requests should be removed when an item is checked out, but that's not the way I'm building it. There are definite use cases for then you want requests stacked so the asset then gets checked out to the next requesting user.
Ah I see, That's OK
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!
This would be a very nice to have feature.
NOT STALE
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!
@inietov haven't we already addressed this? This feels familiar to me.
@jcookatlas Don't yell.
It HAS NOT yet been fully addressed. Yes, A USER can recall/cancel a request but a system admin does not have a method to reject/deny and subsequently cancel a request without asking the user to recall/cancel the request.
t.
@jcookatlas Don't yell.
Wasn't intending to yell - I always respond to bots in caps - its a force of habit.
Also, how hard would it be to make the 'account/requested' page have a self-cancel button so the end user doesn't have to go digging through menus...
I always respond to bots in caps - its a force of habit.
Break the habit. Real live people read these messages.
(Also, you were responding to me, who is profoundly not a bot.)
I was asking an employee here whether we have addressed this (as in, possibly on the develop branch). I have no idea what version of Snipe-IT you're running, so unless you care to provide a little more info, I'm not sure what you're adding here.
(Also, you were responding to me, who is profoundly not a bot.)
I was asking an employee here whether we have addressed this (as in, possibly on the develop branch). I have no idea what version of Snipe-IT you're running, so unless you care to provide a little more info, I'm not sure what you're adding here.
Again, I apologize.
Yes, you are correct, you ARE NOT a bot. In the specific instance of that message, capitalization was used merely for emphasis.
Regarding the additional data: 1) Fresh and clean install on Ubuntu svr v20.04 2) phpver 7.4.3 3) Snipe-IT build v5.3.3 build 6517 (g4afd598df)
I know I've discussed this feature internally, I just don't recall where we ended up with it. Please give me a few.
@snipe @jcookatlas I think it's related to this https://github.com/snipe/snipe-it/issues/8939
But if duplicated records already exist they keep appearing as I fix the bug on the code that causes them but I can't manipulate the data that is already stored.
Pfff, sorry that was only the other issue, here is the actual PR https://github.com/snipe/snipe-it/pull/10053
That said, I think the issue should be closed now... hmm
I have read all the posts about requestable assets. There are a lot of users that need the ability to cancel requests as an admin or clear the request when the asset has been provisioned. As mentioned, there is also a need for the asset to work similar to a library book where everyone's request remains active like in a queue, to wait until the asset is next available.
I have some ideas:
I would be curious to see how people are currently using the requestable asset feature.
I have test the "requestable assets" too. And this is not that what we want. We need to accept and reject.
I also noticed that I can't do anything when I deposit asset models. I don't understand what I am supposed to do there. When I click there, I get to the assets list of this model. Perhaps one could include a query here, if one is available, that one can give it out, if none is available, that one creates a new one.
This feature would be nice! I agree to the others on this issue
I gave up on this a long time ago... sadly.
From: michaelortnersanube @.> Sent: Tuesday, January 17, 2023 2:52 PM To: snipe/snipe-it @.> Cc: ML_IT_Admin @.>; Comment @.> Subject: Re: [snipe/snipe-it] how to remove requested assets (#5243)
I have test the "requestable assets" too. And this is not that what we want. We need to accept and reject.
I also noticed that I can't do anything when I deposit asset models. I don't understand what I am supposed to do there. When I click there, I get to the assets list of this model. Perhaps one could include a query here, if one is available, that one can give it out, if none is available, that one creates a new one.
This feature would be nice! I agree to the others on this issue
- Reply to this email directly, view it on GitHubhttps://github.com/snipe/snipe-it/issues/5243#issuecomment-1384867628, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGLC7XJVWCRZEKIZM54A6ILWSYXQBANCNFSM4EW2ZMWQ. You are receiving this because you commented.Message ID: @.**@.>>
I am waiting for this functionality. It is very much needed
Hi, I would also like to have this feature too. :) Thank you, snipe-it.
a normal user request asset models in requestable menu and a admin user can check it in requested menu. i think that requested assets data will be removed after a admin user check an item out to a normal user. but requested assets model was not removed in the requested assets list.
how to remove processed requests in the requested assets list. is it possible?