Adding options to a custom field as project administrator

I am trying to setup a multi select list custom field 'Client' that contains one value per client. Since we frequently need to add clients it would be nice if the project administrators could do so. Just like they can add versions and components. So far I cna only add values as user with the global administrator permission.

Is it true that only the global JIRA administrator can add values to a custom field? Am I missing something or is there any other way of achieving this (maybe another custom field / plugin)?

4 answers

1 vote

>Is it true that only the global JIRA administrator can add values to a custom field?

Yes, the two system level admin roles can do it. Project admins and lesser users can not. Project admins can maintain compone

>Am I missing something

Nope, you've read it correctly.

>is there any other way of achieving this (maybe another custom field / plugin)?

I think I've seen a plugin that allows you to create "project fields" that the project admins can look after, much like components, but I can't find it at the moment. I'm pretty sure it's recent (4.4 and 5?)

Thanks, I will search for it and report back once I found it.

I have found it (Project Specific Select Field plugin v. 0.5.0 for JIRA 4.3.3 - 4.3.4) but it seems to be no longer maintained by the developer (he did not even reply to my email). Any other solution? Is this still a limitation in JIRA 5?

Have a look at Project Specific Select Field plugin. This addresses your needs. It is a commercial plugin and available for JIRA 5.1 or newer.

Cheers
Holger

Nice plugin, but we are unlikely to pay $3200 for this basic functionality.

I understand your concerns about pricing for Project Specific Select Field, especially if you compare with JIRA itself. But JIRA has a very large customer base and therefore more buffer for a low-price policy.

P.S. It is max. 2400$ for enterprise customers with 10000 or more users.

I understand your concerns about pricing for Project Specific Select Field, especially if you compare with JIRA itself. But JIRA has a very large customer base and therefore more buffer for a low-price policy.

Greenhopper costs $4000 for unlimited users. $3200 for a plugin that allows editing values on a project level is inappropriate. I would price it lower, make people love it, then have Atlassian buy it from you *hehe*

However, good luck with the sales, not everybody thinks like me.

if you won't find any solution then then try with my answer

you can create a table on any data base with the options.

using data base values plugin you can get values from db and add to custom field

the plugin is located here

https://marketplace.atlassian.com/plugins/org.deblauwe.jira.plugin.database-values-plugin

But then you have to give the project admins access (permission + user interface) to this table to add and modify values.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,319 views 14 20
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot