Removing access to a single field gives error when changing status
I want to steer via roles/permission which fields can be changed by whom.
For this I have done the following:
1. Created a new custom field, let's call it 'ABC'
2. Created a new role 'XYZ'
3. Revoked permission from all roles to "Modify the 'ABC' attribute"
4. Granted permission to the role 'XYZ' to "Modify the 'ABC' attribute"
5. Add the role 'XYZ' to all members who should be able to modify 'ABC'
With the above, modification of 'ABC' works as expected. If the user has the role 'XYZ' it works, if not the item cannot be saved if 'ABC' was changed and a respective error message is displayed.
The problem I am encountering: if anyone tries to close the item, i.e. changing the status accordingly, it is not possible to save the item, instead an error message is displayed saying "You don't have permission to perform the following actions: modify/resolutionDate."
Anyone with a clue why this is happening?
|
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Can a user with role XYZ perform the close?
I would consider to open a case with support. Maybe there is an issue with the process.
No user can close the item, not even the ones with the role XYZ.
Where do I open a case with support?
@davyd, I have never been succesful in distinguishing access to single fields based on the error from the initial post.