-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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] Reminder for confirmation through mail #9203
Comments
I also suggested deeper administration of this function. For example, so that the administrator has the opportunity to delete this request. For various reasons, the user does not accept the request and does not follow the link, the asset will be in the list of "not accepted assets". What about rejected assets? The asset will not be accepted and will be available for issuance (will return to the warehouse), and the administrator will not be notified of this in any way. There is no message or corresponding menu item in the program. |
For a start, just permanent reminders to users to sign the "accepted" asset would be very welcome. Along with notifications for those who have not signed within the set period of time. |
Yes,
That would be realy nice. |
Is there any updates on this? I've seen the post above and don't really understand how to implement a scheduled reminder. Is there a way to automaticlly remind people to accept the confirmation? |
Currently, snipe has the option to send a mail to a user who has to confirm with their signature, that they received the item.
In my opinion, it should be possible to see not accepted assets. Additionally, something that would maybe be much more useful, would be an option per asset, to re-send the confirmation mail. The reason for this: In my company our employees are maybe to good trained at deleting mails which they suggest is spam and they often delete the confirmation mails therefore.
Currently, afaik, one have to checkin and then checkout the asset again, to re-send a confirmation mail.
The text was updated successfully, but these errors were encountered: