Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-80771

More Granular Permissions

XMLWordPrintable

    • 15
    • 20
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Hello

      I have been playing around with permission schemes to lock down our projects.

      I have a requirement where I need to give members of my team access to the release tab for a given software project.  They are responsible for creating releases and what goes on when.  The issue is in order to achieve this I need to set on my permission scheme the permission of "Administer Projects" to my developers. 

      When I assign this permission to my developers they can access the release tab which is great.  But this has given them access to other areas which I would prefer they didn't have access to.  For example, they can access the board settings.  We have a custom workflow plugged into our boards and a developer of mine went in and removed a status from a column which made a load of issues "disappear" from the board.

       

      I feel the "Administer Projects" permission needs to be broken down so we can decide what parts of the projects are accessible to the developers.

      Can this be achieved at all?

      We are currently using JIRA Cloud.

              Unassigned Unassigned
              26b51887-174e-4ea2-a41b-a0aef5226c3e Deleted Account (Inactive)
              Votes:
              26 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated: