Required fields different depending on issue type

[Agnieszka Santos]

Hi, 

Is it possible to set required fields different depending on issue type

for e.g. Component for a Story as optional and required for a Task

if I have 2 projects accociated with same configuration scheme and I don't want the same fields to be required for both of the projects what will be the least complicated operation to enable that?

Copy current issue scheme config and name it differently so that I can have 2 separate schemes for those two different the projects and then pick the issues which are meant to be required for both of the schemes differently ?

I wouldn't like to make too much mess, so great is to hear the advise form experienced admins :)

[John Funk · Accepted solution]

Hi @Agnieszka Santos 

Yes, you can do that by creating different Field Configurations for each issue type and then package them together under a Field Configuration Scheme. Then attach/replace the scheme for the project. 

[Joshua Sneed Contegix]

Hi Agnieszka,

John's right, look into https://support.atlassian.com/jira-cloud-administration/docs/configure-a-field-configuration-scheme/ for more info.

Cheers,
JS