Can multiple projects have a custom field that pull from one master list of options?

[keith_vorderbruggen]

I want to have a custom list that is a dropdown field that appears in multiple projects, but they all pull from one source of truth list.  

Specifically, we have teams that are working on multiple applications.  We need a single list that can be maintained and can be used in multiple projects that lists the applications.

Please note - I am not looking for answers that revolve around restructuring our teams or how we are using Jira.  Thank you.

[Jack Brickey]

Hi @keith_vorderbruggen , welcome to the community.

If you are using a company managed project you can certainly achieve this. This is one of the advantages of CMP over TMP. you can check if you are using CMP or TMP in lower left corner.

[keith_vorderbruggen]

We do have CMP.  Can you let me know how this can be achieved?

[Valerie Knapp]

Hi @keith_vorderbruggen , welcome to the community and thanks for your question.

If you are asking if you can have the same custom field list in different projects, yes, this is possible. You would just need to put it on all the screens in the different projects and issue types you want the custom field to appear on.

You can have different custom field contexts so that you could use the same custom field, but have different lists which are specific to the project / context -

Here is the documentation to explain this further - Configure custom field context | Atlassian Support

I hope this helps but if not, please give us your feedback and either I or someone else will try to assist.

Cheers

[keith_vorderbruggen]

Not quite what I need.  I am looking for the field to be the same in multiple projects and all pull from one list.  That way we only need to maintain one list and it will automatically be updated in all of the projects.  I need the values to be identical across projects.

[Valerie Knapp]

Hi @keith_vorderbruggen , you can just have the same custom field with one context that is visible in multiple projects and / or issue types. 

When you create a custom field, you have the option to map it to all the screens where you want it to appear. You can just put it, for example, on the screen scheme for the Issue Type of Epics, and everywhere that scheme is used, in all the projects, they will have the same custom field and the list of values displayed.