Modifying field scheme

[Owen Guion]

Following up on https://community.atlassian.com/t5/Answers-Developer-Questions/Required-fields-by-issue-type/qaq-p/545755

We have several projects sharing a field configuration scheme - for all issue types

Trying to follow-up and split epic and story such that some fields previously deem mandatory for both will now get inherited by story from epic.

The obvious thing given overlap would be to copy the common scheme, then update the field behavior as required.

I am unable to config the fields within the new scheme as it seems to point back to the original field scheme from which was derived - linked vs. copy?

[Muthu Thiruppandy]

You need a separate Field Configuration for Story and Epic, I suspect you copied and created a new Field Configuration Scheme.

If your expected behavior is to have different Required fields for Epic than the story.

 - you can use the same scheme for all the projects ( you can use the one just created by copying..)

- first create new Field configuration, (this is not the scheme but part of the scheme) by copying the configuration already used by story and epic.

- change the required fields in the new  'Field Configuration'

- select your original Field Configuration Scheme.  use the 'configure' screen and 'Associate an issue type with a field configuration' option, to attach the new configuration to the Epic.

Note: this is what works in JIRA server, not sure if anything different in CLOUD