Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-3156

Add additional administrative privileges to users with Administer Projects permission

    • 52
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update – 6 July 2017

      Hi everyone,

      Thanks again for all your votes and comments on this suggestion.

      In JIRA platform 7.3, we allowed project administrators to edit their project's workflows under specific conditions. Now, we're happy to announce that with JIRA 7.4, we added more fine-grained control to the Administer Projects permission, and added a few more perks for the project administrator. When granted, the Extended project administration permission will allow project administrators for the associated projects to edit the project's workflows and screens.

      You can learn more about it here: https://confluence.atlassian.com/adminjira/jira-platform-releases/jira-7-4-x-platform-release-notes

      As the next step, we’d like to hear your feedback about these new capabilities, and the most important features you’d like to see in the Project Level Administration moving forward.

      For this purpose, we've created a new suggestion focused entirely on collecting feedback and ideas for further improvements: https://jira.atlassian.com/browse/JRASERVER-65574. We’ll use it to keep engaging with you on this topic, so please drop all your thoughts there.

      To avoid having multiple suggestions about the same topic, we’re closing this one as fixed. It doesn’t mean that no further work will be done in this area, quite the opposite actually. This will help us streamline your feedback and identify some missing parts that we still need to incorporate into JIRA.

      Thanks,
      Jakub Lazinski
      Product Manager, JIRA Server

      Original request description:

      As a JIRA Administrator I find it more difficult to manage JIRA configuration as my organisation grows. I need to be able to share some of my administrative powers with other people, but I do not want to give them all the management rights, because I am afraid they are going to break things. Each of the projects run in JIRA has its own manager and it would be best if I could give the configuration permissions related to the projects to the respective project managers.

            [JRASERVER-3156] Add additional administrative privileges to users with Administer Projects permission

            Same here - I need to give project admins the ability to create workflows for their own project without exposing all of the work that we do within JIRA!

            Andrew Keil added a comment - Same here - I need to give project admins the ability to create workflows for their own project without exposing all of the work that we do within JIRA!

            Yes, I would like to know the same because we're using the Server version. 

            Earl Zirkle added a comment - Yes, I would like to know the same because we're using the Server version. 

            NOD added a comment -

            That blog entry makes a point of saying "On the Jira Cloud team, we’re working hard to change this."

            Does it apply to the server too?

            Has this Jira ticket for the server been superseded by https://jira.atlassian.com/browse/JRASERVER-65574. I imagine some of the 1500 votes here would apply there – it only has 52 votes so far.

            NOD added a comment - That blog entry makes a point of saying "On the Jira Cloud team, we’re working hard to change this." Does it apply to the server too? Has this Jira ticket for the server been superseded by https://jira.atlassian.com/browse/JRASERVER-65574 . I imagine some of the 1500 votes here would apply there – it only has 52 votes so far.

            Hello,

            This is an old thread, but I would like to know when the capabilities mentioned in this blog will come to JIRA.

            https://www.atlassian.com/blog/jira-software/jira-project-configuration-experience?utm_medium=email&utm_campaign=rss&jobid=103487081&subscriberid=1244755739

            Earl Zirkle added a comment - Hello, This is an old thread, but I would like to know when the capabilities mentioned in this blog will come to JIRA. https://www.atlassian.com/blog/jira-software/jira-project-configuration-experience?utm_medium=email&utm_campaign=rss&jobid=103487081&subscriberid=1244755739

            miikhy added a comment -

            Hi,

            I just released a plugin to delegate group management to empowered users in your instance. You can give it a try here: https://marketplace.atlassian.com/plugins/com.caritteprod.group-ambassadors/server/overview

            This is just a part of your request but I'm sure it would help!

            As it's a new plugin, I'm really interesting in gathering feedback to improve in the near future. Keep me posted if you like it!

            Cheers

            miikhy added a comment - Hi, I just released a plugin to delegate group management to empowered users in your instance. You can give it a try here:  https://marketplace.atlassian.com/plugins/com.caritteprod.group-ambassadors/server/overview This is just a part of your request but I'm sure it would help! As it's a new plugin, I'm really interesting in gathering feedback to improve in the near future. Keep me posted if you like it! Cheers

            Hi everyone,

            Thanks again for all your votes and comments on this suggestion.

            In JIRA platform 7.3, we allowed project administrators to edit their project's workflows under specific conditions. Now, we're happy to announce that with JIRA 7.4, we added more fine-grained control to the Administer Projects permission, and added a few more perks for the project administrator. When granted, the Extended project administration permission will allow project administrators for the associated projects to edit the project's workflows and screens.

            You can learn more about it here: https://confluence.atlassian.com/adminjira/jira-platform-releases/jira-7-4-x-platform-release-notes

            As the next step, we’d like to hear your feedback about these new capabilities, and the most important features you’d like to see in the Project Level Administration moving forward.

            For this purpose, we've created a new suggestion focused entirely on collecting feedback and ideas for further improvements: https://jira.atlassian.com/browse/JRASERVER-65574. We’ll use it to keep engaging with you on this topic, so please drop all your thoughts there.

            To avoid having multiple suggestions about the same topic, we’re closing this one as fixed. It doesn’t mean that no further work will be done in this area, quite the opposite actually. This will help us streamline your feedback and identify some missing parts that we still need to incorporate into JIRA.

            Thanks,
            Jakub Lazinski
            Product Manager, JIRA Server

            Jakub Lazinski (Inactive) added a comment - Hi everyone, Thanks again for all your votes and comments on this suggestion. In JIRA platform 7.3, we allowed project administrators to edit their project's workflows under specific conditions. Now, we're happy to announce that with JIRA 7.4, we added more fine-grained control to the Administer Projects permission, and added a few more perks for the project administrator. When granted, the Extended project administration permission will allow project administrators for the associated projects to edit the project's workflows and screens. You can learn more about it here: https://confluence.atlassian.com/adminjira/jira-platform-releases/jira-7-4-x-platform-release-notes As the next step, we’d like to hear your feedback about these new capabilities, and the most important features you’d like to see in the Project Level Administration moving forward. For this purpose, we've created a new suggestion focused entirely on collecting feedback and ideas for further improvements: https://jira.atlassian.com/browse/JRASERVER-65574 . We’ll use it to keep engaging with you on this topic, so please drop all your thoughts there. To avoid having multiple suggestions about the same topic, we’re closing this one as fixed. It doesn’t mean that no further work will be done in this area, quite the opposite actually. This will help us streamline your feedback and identify some missing parts that we still need to incorporate into JIRA. Thanks, Jakub Lazinski Product Manager, JIRA Server

            Peter T added a comment - - edited

            Greg, I can't agree more. Everyone has its own definition what is safe to be delegated and what not. There are over 200 actions in the administration section. Imagine that you have to configure who has which right and understanding each of the permissions implications.
            I would suggest a different approach with which you can accomplish and delegate any System admin actions and still maintain 100% control of the production server. It is described here: 100% Flexibility and 100% Control
             

            Peter T added a comment - - edited Greg, I can't agree more. Everyone has its own definition what is safe to be delegated and what not. There are over 200 actions in the administration section. Imagine that you have to configure who has which right and understanding each of the permissions implications. I would suggest a different approach with which you can accomplish and delegate any System admin actions and still maintain 100% control of the production server. It is described here: 100% Flexibility and 100% Control  

            I've been seeing all the various recommendations people have given about the level of control project admins should or shouldn't have, and none of them until now have really struck the right balance between their specific business needs and the general business needs.

            Martin's suggestion on the other hand I feel strikes the right balance, and is the starting point that Atlassian should work from. Implement Martin's suggestion, and then go on to allow further administration rights to be enabled/disabled as the global JIRA admin(s) see fit.

            Of course, it'll be another 4 years before even Martin's suggestions are implemented by Atlassian, so I'm not holding my breath.

            Greg Hoggarth added a comment - I've been seeing all the various recommendations people have given about the level of control project admins should or shouldn't have, and none of them until now have really struck the right balance between their specific business needs and the general business needs. Martin's suggestion on the other hand I feel strikes the right balance, and is the starting point that Atlassian should work from. Implement Martin's suggestion, and then go on to allow further administration rights to be enabled/disabled as the global JIRA admin(s) see fit. Of course, it'll be another 4 years before even Martin's suggestions are implemented by Atlassian, so I'm not holding my breath.

            Holger Schimanski added a comment - - edited

            To manage project specific values for custom fields for project admins independend from JIRA admin privilege there are multiple add-ons available

            To manage versions independent from project admin and JIRA admin privilege you can use

            Holger Schimanski added a comment - - edited To manage project specific values for custom fields for project admins independend from JIRA admin privilege there are multiple add-ons available Project Specific Select Field Customfield Editor Plugin Edit Custom Field Values Context Manager for JIRA To manage versions independent from project admin and JIRA admin privilege you can use Version Manager for JIRA

            Wouldn't it make sense to split out some individual features, such as support for project-specific values for custom fields? We also would prefer to see this feature supported out-of-the-box.

            Perhaps some of these features are low-hanging fruit and could be implemented quickly. This issue is so big and the discussion has been going on so long that I doubt whether it could ever be resolved in this form...

            CHD CM Support added a comment - Wouldn't it make sense to split out some individual features, such as support for project-specific values for custom fields? We also would prefer to see this feature supported out-of-the-box. Perhaps some of these features are low-hanging fruit and could be implemented quickly. This issue is so big and the discussion has been going on so long that I doubt whether it could ever be resolved in this form...

              Unassigned Unassigned
              3b1ae0ec93c9 Nick Minutello
              Votes:
              1525 Vote for this issue
              Watchers:
              801 Start watching this issue

                Created:
                Updated:
                Resolved: