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.
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 https://bitbucket.org/hski/projectspecificselectfield-public/wiki/Home) 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,
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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!
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