How to require field in 1 scheme, but not the other

[Chris P.]

This USED to work for me, but now it seems things have changed in JIRA cloud when it comes to "Screen schemes", "Field configurations" and "Field configurations schemes".

I created a new project, using "Share settings with an existing project" flag, as I wanted the same fields, screens, etc from a previous project.

New project gets assigned "Screen Scheme X" (which was scheme in previous project) correctly.

The "Field Configuration" of the new project, gets assigned the "System Default Field Configuration".
I switch this manually to "Field Configuration Y", as I want it to match my original project (do not know why the default gets assigned, not a big issue)

However, there is "Custom field Z" that exists on ANOTHER project, that this unrelated.
"Custom field Z" is flagged as required.

When I go to create a new issue in the new project, I get an notice that "Custom field Z" is required and will not save my issue.
When I use the tool in the "Create Issue" screen > "Where is my field?" = it tells me that "Custom field Z" is a required field in the "Default Field Configuration"

But, "Custom field Z" is not assigned to any of my screens, and I'm using "Field Configuration Y", and not the "Default Field Configuration".

I'm not sure how my project is thinking that "Custom field Z" is related to it in any way, when the screen & field schemes have no reference to "Default Field Configuration" at all.

[John Funk]

Hi Chris, 

Can you edit the Field Configuration to make Custom Field Z not required?

[Chris P.]

Yes I can, but then this affects the other project where it IS required.

I could create a whole new scheme set (screen, fields, etc), but I'm afraid that this will be the norm for every new Project I create, using another as a template.

[John Funk]

Well you can't use a "shared" scheme if you want it to be required on one project and not another that uses the same scheme. You will need to create a new scheme.

[Joe Balacky]

If you make a copy the field configuration scheme from the one that you are using under 'Settings - 'Issues' then you can change the field configuration scheme under the project you would like different requirements for and edit from there.

I assume this has been done but if anyone has any questions let me know

[John Funk]

Hi @Chris P_  -Just following up on this old post. Did you get it solved?

[Crisan Hristea Carolina Sarah]

Hello Chris,

Have you checked if you have any validator for 'Custom field Z" in the new project workflow ? 

Sarah.

[Chris P.]

It is only the  'Custom field Z" set to "required" that is being validated, as, when I switch it to "Optional", I no longer have the issue, but I then affect all the other projects, where this field is in fact "required".