Can Project Specific Select Field have different names in different projects?

We have the following use case:

  • There are several projects that use a Select type cusotm field (let's call it "Customer").
  • The list is very long (ca 100 items) and changes a few times a month.
  • The list is almost identical for all the projects using it, but might differ with 1-2 values.
  • All the projects want to have a different name for this field.

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:

  1. The ability to change the name of this field for each of the projects separately.
  2. The ability to configure the plugin so that only JIRA admins can edit the lists.

Is this possible or planned to be added in foreseeable future?



1 answer

1 accepted

0 votes
Accepted answer

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,716 views 17 21
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