Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Fields configuration [Priority]

Ziv Paskal
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 27, 2019

I will start from the beginning:

I want to have a field called "Severity" that will only be mandatory to fill to an issue of "bug" type. For all the other issues - I do not need this field! ONLY for bugs..

I did not know how to do it so I took the 'priority' field and kind of force it to be the severity field I wanted. It is still called 'priority' but the options are matched for 'severity':1.PNG

I played with the settings and messed things around and now I have a big problem, every time I create ANY issue (story, bug, task, etc...) it DOES NOT show me the priority field but still as a default mark it as a 'Major' even though as you can see above I do not have any default option! Here is an example:

http://g.recordit.co/GsSIQ0RvIe.gif

(please watch to better understand) As you can see no matter what I do there is always a 'priority' field to my issues even though I do not want it to show up!! I only need this to BUG type issues...

To sum up:

I would like to associate this field to be mandatory only for BUGS. For all other issues - I do not need it at all!!!

What can I do??

 

Thank you very much.

1 answer

1 accepted

2 votes
Answer accepted
Joe Pitt
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 27, 2019

Can I have Different Required Fields for Different Issue Types?

Yes, as long as it is a different issue type. Required fields, at creation time are controlled by the field configuration scheme. That scheme is composed of one or more field configurations. Every issue type can have its own field configuration inside the field configuration scheme. If you have 5 issue types and 1 has special needs you create a field configuration for the 4 issue types and another for the 1 issue type. Then you combine them into a field configuration scheme and apply that to the project. When an issue is created, it looks for a field configuration for that issue type and uses it. If it doesn't find one it uses the default in the configuration scheme.  Copy/paste this link for more information. https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-scheme-844500805.html 

Suggest an answer

Log in or Sign up to answer