We have the following use case:
This setup requires a lot of manual changes and synchronization, which is error-prone. Project Specific Custom Field seems to handle the case of having slightly different values for different projects. What we need also is:
Is this possible or planned to be added in foreseeable future?
1. No. It is similar to standard custom fields. You need to add multiple instances of Project Specific Select Field - one for each name, then create different field configuration schemes and hide / show these fields.
2. Give the JIRA admins the permission "Administer Project" in the permission scheme. Then assign your jira-admin group to this permission.
But if you want the JIRA admins to change the field values, why do you need Project Specific Select Field? You can do this with a standard Select custom field.
The benefit and use case of Project Specific Select Field is, that a project admin can configure the values of the field and he can configure it project specific (what is available with Standard JIRA with config contexts only by JIRA admins.)
Why we need such a field was explained in the first 4 bullet points. The main idea is to have just one single field instance with different name labels and slight variation in different projects.
This would greatly reduce the overhead of managing multiple fields with many values that change a lot (but need to be in sync mostly). In order not to make a mess of it in an enterprise environment, it would be good if only jira admins would be able to modify it.
As I understand, this field is directly tied to Administer Project permission?
Anyway, I got the answer to my main question - this is not doable with Project Specific Select Field.
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