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

Separate Priority Schemes for each issue type

User wants to use a different Priority scheme for one Issue Type while using the default priority scheme for all other issue types.  Can this happen & how?

1 answer

1 accepted

0 votes
Answer accepted

No, priority schemes have only just been changed from global to project.  They can't be issue-based.  (I'm not sure they ever would - if you have very different priority schemes in a project, you probably should be using separate projects)

Thank you Nic:  I suspected as much.  In this instance, the users want to use a numeric scale from 1 - 5 for a BUG issue type but retain the default priorities for the other issues.  More specifically, they are testing hardware & software combinations and will be identifying bugs in both.  I understand the dilemma as no matter how granular a project team may be with respect to their areas of responsibility, occasionally you do have issues that fall outside the parameters of your project structure.  I will have to offer an alternative solution that will satisfy all their needs.

Hi, Nic.

Long time no speak! :) 

Is it possible to remove the default Jira priority field from a Project? I've removed it from the Create Issue screen but as soon as the issue is created it appears on the actual issue.

I've created a custom priority field to use for this Project and so it is a little confusing to still have the default Priority field showing as well.

Can you help?

Thanks,

Adam

You can use the "field configuration" to hide the priority, which will also stop it taking any value on create/edit. 

But I think it's like resolution - once set, the priority will still appear whatever you do.  (Not a bad thing for resolution, as that should never be hidden, at least until Atlassian move to a sane "done"/"closed" scheme)

You should be able to bulk-edit to clear the existing priorities (before hiding it with a field configuration scheme).  

Try hiding it first though! 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

261 views 1 2
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