Before I make something so simple, woefully complex and potentially service breaking (!) - I wanted to know how best to add the functionality to a standard JIRA user for them to change the Priority in tasks?
I've been looking into custom groups, permissions for software schemes, field configurations, etc - but nothing seems to quite fit the bill. I just want one user to carry on as he is, but also have the ability to change the Priority value on each ticket.
Any suggestions would be much appreciated.
Hi Jack - thanks for the response.
The user is currently in the access-jira default group and can alter the status of tasks from To Do, In Progress, etc - which is fine and we want him to carry on doing that.
However, we'd also like him have access and the ability to choose from a custom field radio button selection called CAB Priority which has five options.
I think as it stands, the status of the tasks isn't Editing the task as such and is therefore allowed. But to give the user access to change the value on a custom field, is?
Realistically, no - there isn't a reason. I didn't really look at the project permission level as the user in question could potentially cross projects - so I didn't want to muddy the waters that way.
I guess JIRA was implemented at our site with the view that we'll restrict everything as much as possible and only increase access rights as they are required. Probably not the best method!
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events