Always display certain fields when creating an issue

[George McCurrach]

We will only use certain fields in our Jira project.  I would like to make it easy for our team to know which fields they need to fill out (and which ones they can leave blank) when creating an issue.  I notice that when I select "create issue" there is a "configure fields" button, and when I select 'custom fields',  I can check or uncheck certain fields.  I was thinking we could have each of our users do a one time setup where they could check only our required fields (and leave the rest blank)...and then this would prompt them to fill out only the necessary fields.  But when i tested this, I saw that my checks change over time (some are no longer checked).  Is there a way to keep the checks from changing?

[Joe Pitt · Accepted solution]

You need to create a issue field configuration. That is where you mark fields required upon creation. Jira can have 3 screens, create, edit, view. The create screen are the fields you want or require to create the issue. The edit screen normally has fields the team needs to update, the view screen would normally have all the field from the edit and create and fields set behind the scenes by post functions or other automation. 

[George McCurrach]

thank you.  I see that there's a "Screen Scheme" for each issue type....and underneath this is "Create", "edit", "view".  Looks like this is what I need to customize?

[Joe Pitt]

Jira is broken down in to schemes and configurations. First you need a Field Configuration. Here is a short summary of them.

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 

Screen Schemes are what screens are shown for each issue type. That is where you assign the create, edit, and view screens after you create them. 

[George McCurrach]

thank you very much, I appreciate it!