Is there a limit to the number of values the Project Specific Field can have before it stops working as a tab on the Project page? I have a field that has more than 900 values for a project and more than 1100 for 2 other projects. Clicking the Project Specific tab on the project page for those projects results in a timeout error.
Project Specific Fields plugin: 2.0.4
I was not aware, that there a custom fields used with this amount of option values. The tab runs into a timeout error, because for the custom field statistics (bar chart) a count of issues is done for each option value. That means a lot of JQL queries. And also the HTML page itself gets big.
How about restricting this custom field statistics to first 50 option values? Or drop the creation of the count and bar chart for a custom field with more that 50 values?
What would you prefer?
So there is no UI-based way to chagne the value of a project-specific field option unless each project has its own configuration scheme? I did not create a field configuration scheme for each project, as I have 85 projects and each needs its own set of values. This is a major oversight.
Sorry, all what I was saying about changing option values via JIRA admin UI is only valid for Project Specific Select Field and Project Specific Multi Select Field. For Project Specific Select Field (simple) you as a project admin have to create a new option value, change corresponding issues via bulk change to this new value and then disable the old value. There is no direct edit available.
In general Project Specific Select Field and Project Specific Multi Select Field have many advantages (see https://bitbucket.org/hski/projectspecificselectfield-public/wiki/Home with section about Deprecated Custom Field Type). You should think about migration from Project Specific Select Field (simple) to Project Specific Select Field resp. Project Specific Multi Select Fiel. But I must say, that currently there is no real support for this, then just creating a new custom field by hand and then migrate via bulk change. Another customer requested a migration tool or at least some REST API to do this via scripting, but implementation is tricky for this. Please comment and vote there if interesting for you.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot