-
-
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]: Show EOL Date to the User #15103
Comments
Hi @SebastianKlimczok & @huifei0129 +1 from my side However, @huifei0129: Your solution does not work for us. We have the same problem as Sebastian. Our end users should not see all the equipment of their entire company. Every user should only see the devices checked out to him or herself, but be able to see how old these are. Perhaps I am just to stupid to give a user view permission to the users assets only? How would that work? But then again, this would give them permissions to see the history, notes and stuff as well? And not sure if my clients feel well with that... So would definitively be nice if I could add a few columns to the assigned asset page for end users and show them the EOL of their devices, in order to enable them to plan ahead any device exchanges (people get pretty serious about getting new stuff!) |
Fixes #15103 - Added EOL and audit into to user profile assets
This is now on master and will be in the next release. |
Is your feature request related to a problem? Please describe.
Currently in order to know, when a device is EOL or over the minimum usage time and has to get exchanged, the user has to ask us directly. There is no way to show the EOL Date directly in SnipeIT to the user.
Describe the solution you'd like
An option to enable the EOL date on the User view-asset#asset page in the checked out asset table
Describe alternatives you've considered
Showing other column for a similar purpose (e.g. Expected Checkin Date)
Showing custom fields with references to the current date (e.g. checkout date + 3 years)
Additional context
No response
The text was updated successfully, but these errors were encountered: