Project Specific Multi Select Field requiring options when creating the field in JIRA 6.2.x
Issue #32
new
In JIRA versions 6.2.x the multi select PSSF is requiring options to be added at the moment of the creation of the custom field. Once created the options added during the creation and any other option added later in a specific project are available in all the projects.
I've attached some screen shots of the creation process.
Comments (7)
-
repo owner
-
repo owner
As a work around please go to JIRA standard custom field administration page after creation of the field and remove this initial option value.
-
reporter
I've tried the suggested workaround, but even deleting the initial option value when I add a value for a specific project that is appearing in all of them.
-
repo owner
By default JIRA creates a global custom field context. But you need to create a custom field context for each project (!), which should be able to use the custom field. This context is used to store the list of option values for the project.
You can also create a custom field context for a set of projects (or even a global context). This means, that all projects part of this context share one list of option values. This is what you currently have configured and therefor all added options appear also in other projects.
Hope this helps?
-
reporter
Hi Holger, thanks for your reply, the workaround works but that could also be applied to a standard multi select. Somehow with previous JIRA versions that was not required. Is there any plan to fix that in the near future?
Best regards, Antonio
-
repo owner
This is a know issue and reported as JRASERVER-37309. It is there since JIRA 6.2. I know of other plugin vendors talking to Atlassian about this issue, but I guess we have to accept it.
Best regards Holger
-
repo owner
In JRASERVER-37309 there is an interesting information by a user about how to possibly prevent this situation.
Maxime Lefebvre on 27/Oct/2020 2:53 PM
We found out that the options are required at creation when the option configuration item is present in the custom field configuration screen (in `getConfigurationItemTypes`).
A workaround would be to replace the `SettableOptionsConfigItem` from your config items to something else.
Not really sure, what this means, but could be a chance.
- Log in to comment
This is standard behaviour in JIRA 6.2 now. This is the case also for standard single and multi select field and not only Project Specific Select fields. I don't see any possibility to get around this. Maybe it is useful if you get in thouch with Atlassian to change this back to non-required?