Allow project admins to add or disable to project specific custom fields. Restrict them to delete any option from the fields

[Jeetendra]

Hi,

Recently we have a serious problem with Project Specific fields in Jira.Some project admin deleted the options from project specific fields and the issues have lost the data with respect to the field. This is big problem for us

our request is:

1. Please allow Project admins to add or disable the options from a project specific fields
2. Restrict them to delete any option from the project specific fields

Please provide a fix for above concerns

‌

[Holger Schimanski]

Thanks for getting in contact. I understand your situation, but isn’t this the same for versions and component? Project admins are also able to delete those. Are you restricting project admins also to not being able to delete those?

When a project admin is deleting a project specific option, then he get’s a warning message of affected issues. So it should not be of surprise for the project admin about the effect on issues. Do you think this is not sufficient? This is by the way same behavior as for delete of versions.

[Jeetendra]

Hi

Thanks for your quick response

In case of versions and components it is project specific and Project admins for a specific project are responsible. But in case of project specific custom field the field is used by different projects.Hence we are unable to know which project admin or project has deleted the options.

That’s why we need some restrictions for project admins

Could you please add my colleagues as watcher to this ticket

[e-mail]

[e-mail]

[e-mail]

Thanks

Jeetendra

[Holger Schimanski]

Have you considered having multiple custom field contexts? This would be a common setup, where every project get it own custom field context and by this has its own list of option values, therefor such side effects should not happen. See documentation here https://bitbucket.org/hski/projectspecificselectfield-public/wiki/Home