By default, the "Default Field Configuration" is attached to the "System Default Field Configuration" on new projects in JIRA.
However, this means all Issue Types on any project using the above set up will share the same Field Configuration.
Without having to create a new "Custom Field Configuration Scheme", is there any way of editing the "System Default Field Configuration" so that certain Issue Types can point to another Field Configuration other than the "Default Field Configuration"
Hope that makes sense. Thanks in advance.
Hi Gary, if I'm understanding your question correctly, that's what Field Configuration Schemes are for. You can use a Field Configuration Schemes to point some issue types to a specific Field Configuration and other issue types to a different Field Configuration, within a certain project.
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."
Yes, you can edit the settings of the default configuration(s), but if you only have one, it will impact how fields are treated for all issues.
Is that what you mean?
There's more on Field Configuration Schemes here: https://confluence.atlassian.com/adminjiracloud/associating-field-behavior-with-issue-types-776636450.html and on Field Configurations here: https://confluence.atlassian.com/adminjiracloud/specifying-field-behavior-776636443.html
Hope this helps,
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot