Say I want to add a checklist custom field from an addon to a single issue type. I would create a field configuration based on the default, adding the checklist to it and associate the new field configuration with the issue type I want.
Risk with this is that once the default field configuration used for all other issue type is changed - the changes do not propagate to this extended one, since it's a dumb copy, not really an extension of a living original.
What is the correct approach to this?
In the end, what I wanna do is to have all issue type still use the default field configuration, but each would be associated with additional subset o different custom fields. Can I not have all of them share a basic field configuration and then each having their own extended set of other fields?
Found out just after posting the question. Actually pretty simple:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.