Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Simple priority permission

Hi,

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.

Regards,

Darren.

2 answers

2 accepted

0 votes
Answer accepted
Jack Community Leader Jan 07, 2021

Priority permissions are associated with the Edit issues permissions. Are you saying the user has the ability to edit the issue but not the Priority?

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?

Thanks,

D.

Jack Community Leader Jan 07, 2021

Correct. Have you inspected the project Permissions? Is this NG or Classic? Is there a reason why you would not want the user editing other fields?

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!

0 votes
Answer accepted
Sandesh Shetty Community Leader Jan 07, 2021

@Darren Smith 

Generally anyone with the edit issue permission in the permission scheme will have the ability to change all the fields in edit screen including priority.

Thanks and Regards

Sandesh

I've ended up giving him the relevant permissions within the project and it works fine.

Thanks for the suggestions - gives me something to work on moving forward should we need more changes!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

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 ...

7,073 views 8 28
Join discussion

Community Events

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

Events near you