Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-16286

Improve 'Manage Sprint' permissions when the filter is complex re JSM projects

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • 2
    • 38

    • 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.

      Problem Definition

      Currently, as explained in Using Manage Sprints permission for advanced cases:

      When boards have complex filter queries
      A filter query is considered complex when Jira Software can't determine which projects will be returned by the query. When this happens, Jira Software will require users to have the 'Manage Sprints' permission for all projects in the instance — essentially, you'll need to manually set users to have this permission for all projects.

      This means that the users also need to have Manage Sprints permission in the JIRA Service Desk projects as well as have JIRA Service Desk licence.

      Suggested Solution

      Improve Manage Sprint permissions when the filter is complex, so that the user doesn't also needs a Service Desk licence.

        1. Manage Sprint permision in a JSD project.png
          Manage Sprint permision in a JSD project.png
          68 kB

            [JSWCLOUD-16286] Improve 'Manage Sprint' permissions when the filter is complex re JSM projects

            There are no comments yet on this issue.

              Unassigned Unassigned
              mgocevska Maja (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: