Server (please complete the following information):
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Hi,
My english is bad :)
I have created an authorization group, group cannot edit asset maintenances. How to edit asset maintenance
Thanks...
You haven’t explained what you’re seeing here. What are you trying that isn’t working? What permissions does the user and group have? What error message happens when they try?
hi,
assigned authority : Assets: View full
but asset manintenance cannot edit
asset maintenance edit not active,
except super user, with which authority I can make active ?
thanks
@snipe did I explain the problem?
Same Problem here.
A bunch of Users is in a Group with every Right granted except "Global: Super User" and "Consumables: View" but don't have the ability to edit the Asset Maintenance.
There's no explicit Right to grant them in the Asset Section of the Permissions.

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
Answering on Stale: Problem still exists, would need a more granular right management.
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!
Same, issue all non super users are unable to edit assets maintenances.
its a bug, a user who can add maintenance should be allowed to edit the maintenance details.
User A: added maintenance and accidently added cost as $190 instead of $90 in such case the user is not able to correct this mistake. Only super user can edit it and correct the mistake.
ver: 4.6.6
Apache
PHP 7.2
We are seeing the same behavior on our installation of users being unable to edit asset Maintenances.
v4.6.16 - build 4018
CentOS 7
Apache 2.4.6
PHP 5.6.40
FYI: I just ran into this issue as well. Version v4.7.4 - build 4107
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
need this feature too.
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!
Please dont close. We need it.
On Sat, 31 Aug 2019, 10:38 pm stale[bot], notifications@github.com wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/6787?email_source=notifications&email_token=AAAZRYHXNW4DMURHLZEVMILQHKUAHA5CNFSM4G4BWX32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5TRYTQ#issuecomment-526851150,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAZRYANT2M52LEZRBXRUM3QHKUAHANCNFSM4G4BWX3Q
.
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it.