Field Configuration changes - why?

[Darryl St_ Pierre]

This is a Why question rather than a How...

I'm working on a request to require certain fields for certain issue types in specific (Company Managed) projects. The very first thing I did was to create copies of an existing Field Config and Field Config Scheme.

While working on the (copied) Config, I decided to clean up the many screens that showed as associated. I assumed this was safe because these copies were not associated to any projects. Within minutes I get a call saying the field has disappeared from screens.

I restored the screens and all is well, but if I'm working in a separate config that is not associated to any projects yet, why did this happen?

Thanks for any insight you can share.

[Mikael Sandberg · Accepted solution]

The reason this happened is because the association to screens are shared across all field configurations. It is controlled from the field, not from the field configuration. So if you remove a screen in one field configuration it affects all of them.

This is a good overview of how it is all tied together, it is from the DC documentation but it applies to Cloud as well.

[Darryl St_ Pierre]

Thank you Mikael. Sorry I didn't see your response earlier.

I get it, and the association makes sense. I even expected the answer you posted after thinking about it for a while. I guess I'm just annoyed that I was so easily allowed to modify a configuration outside the scope of what I was working on.

Your answer is appreciated.