Restirct Project specific options management

[Abinash Satapathy]

Hello Holger ,

Currently we are using Project Specific Plugin in our many Jira Projects . The plugins greatly helps Project Admins in managing the options for their Custom Fields but we have a situation now within our Application.

In our project we have a lot of Admins and we don’t want to give the possibility to each and every admins to manage Options in a Project Specific fields. It will be beneficial if we can allow member of certain group

[Holger Schimanski]

Thanks for getting in contact! To have a full picture of the use case, may I ask what tasks these smaller admin should be able to do?

• Create versions
• Create components
• Add or remove people from project roles
• Create sprints
• …

‌

‌

[Abinash Satapathy]

Hello Holger ,

Thanks for your reply .

Answer to your questions:
The small group of admins should be able to perform all activities which is usually carried out by a admin ( Create Versions , Components , Manage Sprints ,Etc) but they should have the special permission to manage the Options in the Project Specific CF’s .

To Simplify my question : How to not give the permission to all Project administrators in a Project to manage the options for a Project Specific Field .

Regards,
Abinash

[Holger Schimanski]

I am sorry, it is currently not possible to restrict the permission. Currently all project admins have this capability. To provide this capability would be a major enhancement of the authorization concept and I am not sure, because it would complicate the things for the standard use case and every Jira sys admin to understand the plugin.

I am thinking if you could revoke project admin permission from the ones who should not becable to manage option and provide them other ways to do their job as a non-project admin.

• For create versions, then I would recommend my other plugin Version Manager for Jira to give non- project admins the power to manage versions.
• For creating sprints you could give this permission via Manage Sprints permission to non-project admin people.
• Creating components is typically not happening this often, therefor maybe could be limited to the

Maybe this is an option to consider as a solution for your requirement. (I would give you a very high discount on Version Manager for Jira )

[Abinash Satapathy]

Hello Holger ,

Thanks for your answers. We used your suggestion and removed members from admin role.

Regarding Version manager , unfortunately we don’t have any business case for this plugin.

But thanks for the offer .

Regards,
Abinash

[Holger Schimanski]

Okay, thanks for the feedback. I close this ticket now, because we found a solution.

See also #63 for similar request.

Best regards,

Holger