[#JRA-5749] maintenance of custom field parameters

JIRA

maintenance of custom field parameters

Created: 25/Jan/05 01:09 PM Updated: 20/Jun/08 03:59 PM

Component/s:

Administration, Custom Fields

Affects Version/s:

3.0.3

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-14615~~ Allow jira users to update values of select-list custom fields

Reference

This issue relates to:

JRA-3156 Required: Project Group Administrator

Participants:	Bruno Busco, Claire Chardiny, Eric Hoffmann, Jeff Turner [Atlassian], Steve Host and Tim Dawson
Since last comment:	4 weeks, 1 day ago
Labels:

Description

« Hide

currently only a JIRA Administrator can modify the list of selection parameters available for a custom field. project managers need to be able to modify the values for project-specific custom fields the same way they can modify the list of versions and components.

My apologies if this is a duplicate - I assume someone would have asked for this already but I was unable to find any related issues.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 28/Jan/05 02:07 AM

Yes, that sounds reasonable.

Thanks for the report (AFAIK it's not a duplicate).

–
ATLASSIAN - http://www.atlassian.com
-
Like our software? Tell your mates and you can win an iPod photo
http://www.atlassian.com/mates

[ Permlink | « Hide ]

Steve Host - 09/Mar/05 08:41 AM

I am having the exact same problem. We are an enterprise customer with multiple projects each with their own requirements. I would like to offload administraiton and modification of forms to the lead developers on each project. Parameters for most projects are very dynamic and require periodic or sometimes constant updating.

[ Permlink | « Hide ]

Bruno Busco - 21/Jun/07 05:29 PM

In our application we have this problem also.
We need to control the possibility to edit a custom field option list as any other permission. In this way the "custom field option list edit" permission could be granted not to the project administrator only but to any other project role.

[ Permlink | « Hide ]

Claire Chardiny - 13/Mar/08 03:01 AM

As I said in ~~JRA-14615~~ , It could be useful to archive retired values depending on roles or permission schemes :

Then we could:

keep the old values in existing issues
limit the list of accessible values at creation/edition (but not for the search) - could be dependant on the context of the custom field
avoid non adminitratror users to supress values permanently by accident

[ Permlink | « Hide ]

Eric Hoffmann - 20/Jun/08 03:59 PM

In our application I want users with project-admin permissions to add values to a custom field which contains customer names. Currently, I'd have to give everyone admin permissions or manage it myself which is to burdensome.