Is it possible to not add new context when creating a Project Specific Custom Field?

[Orawan Sittakom]

It seems steps to add a new project specific custom field has been changed after we upgraded the plugin from v.1.0.0 to v.2.4.1.

In v.1.0.0, when we created a new Project Specific Select Field, the project admins could manage their own list of option values. The option values of each project were independent of each other.

But when we upgraded to v.2.4.1, when we created a new Project Specific Select Field, we're required to add a new context per a project so that project admins in each project will be able to manage their own list.

But our problem is, currently there are more than 600 projects created in our JIRA. It's very difficult for us to create contexts for more than 600 projects.

Do you have any suggestion about this? Or we should be back to use Project Specific Select Field (simple) as we ever used before.  

[Holger Schimanski · Accepted solution]

Yes, you are right. This manual creation of the 600 contexts for the 600 projects is a problem. That's why next major release will add functionality to Bulk creating of custom field context per project and Creating custom field context should be available via API / REST.

As a work around you could try to script the JIRA admin UI via curl, but that we a bit tricky because creating custom field contexts is not directly available via JIRA REST API.

You could stay with Project Specific Select Field (simple) for time being and while waiting for the next release.

Best regards
Holger

[Orawan Sittakom]

Thank you for your answer.

one more question about this.

To allow bulk creating of custom field context per project, will it be cause of the performance issue if a custom field has more than 700 contexts added or more than 1,000 contexts added? 

[Holger Schimanski]

I don't think so because Atlassian has customers with really big installation and they also do load testing, but of course depends also on your JIRA and database setup. Maybe you contact JIRA support and ask there. That feature is nothing special to my plugin. Therefore they should be able to give some statement.

[Holger Schimanski]

And would be nice, if you could post their answer here as well. :-)

[Orawan Sittakom]

Thank you! You can find information below: Atlassian mentioned that there should be no performance issues with having multiple contexts added into a custom field as far as he know. Just ensure that the minimum requirement for the hardware is set up correctly, see https://confluence.atlassian.com/display/ENTERPRISE/JIRA+Sizing+Guide