I can't make a issueType relates to other than System Default Field Configuration in jira cloud

[David Peles]

I have created a custom IssueType so that certain Issue Type can point to another Field Configuration other than the "Default\System Field Configuration". I created a new "Custom Field Configuration Scheme" and relate it to the custom IssueType. But Jira still keeping the configuration on the Default\System Field Configuration and not the new one I created after I did the 'Use a different scheme' and 'Associate'

Why? what do I need to do in order to fix it? 

Here is a Use Case for what I want as a result  :

In the project called "Development", I want the custom field "Environment" required when the issue type is "Bug."  In the project called "Support", I want the "Environment" field to be optional when the issue type is "Bug."

[Angélica Luz]

Hello David,

Thank you for reaching out to Atlassian Community!

The Default Issue Type Scheme is a system scheme and it’s not possible to remove issue types from this scheme. 

I understand that you need that specific fields as required for specific issue types and I believe that using a workflow validator for that would be easy.

A field configuration is associated with an entire project, so unless your project has only one issue type, it will not be possible to achieve what you need because once you mark the field Environment as required, for example, it will be required for all issue types of the project.

• Allow more than one custom field context to be associated with the same project but different issue types

Regarding my suggestion, you will have to add a specific workflow for the issue type Bug. If you want it to have the same workflow as the other issue types of the project, you can create a copy of this workflow, so you can edit and associate it with the Bug issue type only.

If the issue type doesn’t have a specific workflow:

1. Go to Cog icon > Issues > Workflows.

2. Click on Copy for the desired workflow. In my case here, I added Bug in the name just for it to be easier to find when associating. 

3. Once you click on Copy, it will open the workflow for you to edit. The workflow is inactive, so it won’t affect anything on your project or site. 

4. Click on Diagram and then select the transition that you need the field to be required > Validators.

5. On this page, click on Add validator > Field Required Validator > Add.

6. Then, select the field > Click on add > Add an error message (optional) and click on Add again. 

Since it’s an inactive workflow, you can’t publish it, but the modifications are saved automatically.

7. Now, go to Projects > Select the desired project > Project settings > Workflows > Add workflow > Add existing.

8. Select the workflow you previously copied > Next > Select the issue type Bug > Finish. 

9. Once you do that, on the top of the page it will show the option to Publish, so click on it to save the changes and activate the new workflow > Associate > Acknowledge.

10. Now, when someone is creating a ticket, if they don’t add a value to the field, it will show the error message.

If your issue type already has a specific workflow, you just need to edit the workflow, add the validator and publish.

Hope this helps!

If you have any other questions, please let us know.

Kind regards,
Angélica