Can an issue type be associated with an extension of a default field configuration?

[simon democko]

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?

[simon democko · Accepted solution]

Found out just after posting the question. Actually pretty simple:

1. Go to Issues administration 
2. Custom Fields
3. Find the custom field and press configure
4. Applicable contexts for scheme: Edit Configuration
5. Select desired issue types where you wanna see the field, you can also select the projects to apply to.