Can I define a custom field context per issue type?

[Bp SchTon]

 I want to reuse custom fields as far as possible. Example is a field named "class" which should e.g. take the options

- "functional" or "non-functional" for my own issue type "requirement"

- "TN" or "ICD" for my own issue type "document"

and that independent of the project this custom field is used.

[Trudy Claspill · Accepted solution]

Hello @Bp SchTon 

Welcome to the Atlassian community.

Custom field contexts can be specified based on issue type(s) combined with project(s), so yes you can have a context that is specific to an issue type, associating that with either all projects or 1..n projects.

[Bp SchTon]

Thanks a lot for your prompt answer. Yes, I know that I can associate the context per project. But then I have to update the context whenever a new project  is created.  Correct? There is no such way to say whoever is using a given issue type in a project automatically gets the options for this issue type?

[Trudy Claspill]

Only the original, default context for a field has the option above the Projects list to select "Global".

If you add another context for another issue type for that same field, you have to explicitly pick the projects to which that context will apply.

You might be able to use an Automation rule with the Project Created trigger and the Send Web Request action to call the Issue Custom Field Context REST API  endpoint and update field contexts to include the new project.