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

Having a separate permission for Active sprint and Planned sprint

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Tracked Elsewhere
    • None

    • 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

      Problem Definition

      At the moment, Adding issues into sprint requires Edit issue permission. This is applied for both active sprint and planned sprint

      Suggested Solution

      It would be great to separate permission for active sprint and planned sprint. This would be helpful in the following scenario:
      We want to restrict user to add or move issues to active sprint , but they should still be able to add issues or move issues in future sprint and backlogs.

      Attachments

        Issue Links

          is incorporated by

          Suggestion - JSWCLOUD-8964 Specific permission to add an issue to a Sprint (or remove an issue from a Sprint)

          • Gathering Interest
          is related to

          Suggestion - JSWCLOUD-5035 As a JIRA/GH administrator, I would like to be able to specify who is allowed to create and start a sprint independently from the "Administer Projects" JIRA permission

          • Closed

          Activity

            People

              Unassigned Unassigned
              azuhra Aqqiela
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: