Project specific custom field does not work

Hi All

We have project specific custom field installed on our JIRA instance.

We defined a custom field 'Teams' (project specific custom field) and enabled it for two projects A and B

Now in Project A, if someone adds or disables any Teams Option then that change also gets reflected in Project B. And the same vice versa.

My understanding was that project admins can define custom field option for their own project and that should not affect globally justlike components field.


1 answer

To get project specific options for a custom field of type Project Specific Select Field, after adding the custom field, you need to create one custom field context per project. (See By default a "global" context is created by JIRA. Please delete this and and one per project. This is an annoying thing to do for 400 projects, but it is a one-time effort.  

By the way, is there any chance that you update to version 2.4.1 of the plugin, because it contains major refactoring of the user interface and new features?

Hope this helps,

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

740 views 1 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you