A copy of a field configuration affects the the original

Carl-Erik Kopseng_6xtr0v

In our installation, we have one field configuration that applies to most screens. I wanted to have a slight twist on this config, and as I am new to field configurations, I thought I would start by copying the existing field configuraton so that my changes would not affect the existing settings. 

That was a wrong assumption.

Basically, the only thing I wanted different for one of my projects was making Components a required field. So after opening my new field configuration and making sure it only applied to a screens in my project, I went back to the original and saw that the changes were reflected there as well! It was as if every change was global.

I do not understand what a field configuration is if the changes are not scoped to the field configuration, but is applied globally across all field configurations. 

Niranjan

Hi @Carl-Erik Kopseng ,

Let me try to explain. Technically field configurations are not closely related to the screens, but to the issue types in the project.(but screens are linked to issue types). You basically create and associate different schemes( Workflow scheme, screen scheme, Field configuration) for issue types ( either a shared workflow scheme or separate schemes).

What could have gone wrong with the changes that you had made? Anything. We would need more information, but if you have applied the change in the default Field configuration instead of the copied one - Yes that might have been the issue.

 

The ideal way to approach the use case is

1. Make the field optional in the Field configuration
2. Take a copy of the field configuration
3. Create a Field configuration scheme - "Add Field Configuration Scheme"
4. Associate the Copied Field Configuration to the new Field Configuration Scheme.
5. Associate the FC scheme to the project. Now your project has a separate Field Configuration Scheme, which in turn would have a dedicated Field configuration. ( The field configuration would show "shared by 1 project" and that should be yours..)
6. You can now make changes as required.

https://confluence.atlassian.com/adminjiracloud/adding-editing-and-deleting-a-field-configuration-844500796.html

Apologies for the lengthy reply :P