How to make the 'Component/s' field required only for a certain issue type screen?

[Quality Assurance Traffic]

I want the "Component/s" field mandatory only for certain issue type screens. Not when I'm creating an "Epic".

I've created a separate screen scheme for Epic, and associated Epic issue type with different screen scheme, but didn't work.

The scenario I wanted to implement is that multiple Bugs / Suggestions / Concerns / New Features should appear in Epic. Whereas, Component/s field is required to mark the Bugs / Suggestions / Concerns / New Features.

Attached are the snapshots. Is it possible that the Component/s field would become non-mandatory whenever I'll create Epic?

Any help will be appreciated!

Thanks

  

[Nic Brough -Adaptavist- · Accepted solution]

Jira's mandatory/optional flag is not done in screens.  The field configurations hold the flag.

What you need to do is have two field configurations, one with the component set mandatory, and the other without it.  You then use a "field configuration scheme" to say the Epics use the scheme where it is optional, and the other issue types use the one where it is mandatory.

[Quality Assurance Traffic]

Thanks Nic for your prompt response.

Just like that?

What else need to be done?

[Nic Brough -Adaptavist-]

Yes, you're nearly there.  You need two field configurations, then tie them together and apply it to the project with a field configuration scheme.

[Quality Assurance Traffic]

Thanks, that worked!

[Guiomar]

Hi there,

How did you do this last step?

I configured two field configurations to have Component mandatory in one of them and the other one to have it Optional. Now what I don't find it is how to assign it to Epic type in the optional case via the field configuration scheme. Can you help?

Thank you,

Guiomar

[Nic Brough -Adaptavist-]

You set it as optional or mandatory in a field configuration, then tell the project to use that field configuration for Epics in the field configuration scheme.

[Guiomar]

Thanks, Nic. 

I was not finding the Associate an issue type with a field configuration button.

Worked!