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

Project "sub-commanders"

    XMLWordPrintable

    Details

    • Feedback Policy:

      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.

      Description

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

      The main reason why I end up creating additional permission schemes is to allow specific users elevated rights for a particular project. This is quite a common need, as project leaders often need to delegate certain tasks. An example is delegation of "defect management" for a project. Ordinarily, on the assignee, reporter and project lead can edit or re-assign an issue. However the defect manager needs to be able to do this for any issue in the project.

      Basically what is needed is a built-in per-project group called "Project Admins" or similar. It would be different for each project (like the project lead is), but could be assigned permissions globally within a scheme.

      Alternatively, you could allow permissions to be assigned to the group of Component Leads (implicitely per-project).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              d18eb5d46d35 Martin Rothbaum
              Votes:
              8 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: