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

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.  

2 answers

1 accepted

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

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? 

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.

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

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

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Jul 10, 2018 in Marketplace Apps

If you’re an Atlassian app developer, you’ll want to know about Atlas Camp!

This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...

183 views 0 4
Read article

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