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

Specific permission to add an issue to a Sprint (or remove an issue from a Sprint)

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

      Currently, only user with Edit Permission in the projects able to add issues to sprint.

      However, there are some use case where by projects are interrelated and the other project dependent on other project's issues to be resolved. So, having the ability to nominate an issue to be fix in the next sprint in another project is important in this scenario.

            [JRACLOUD-90787] Specific permission to add an issue to a Sprint (or remove an issue from a Sprint)

            +1

            jose.fortich added a comment - +1

            Dan Jury added a comment -

            This would be very useful for us as well.  The ability to manage and control an active sprint is essential.

            Dan Jury added a comment - This would be very useful for us as well.  The ability to manage and control an active sprint is essential.

            It doesn't seem that the description of this issue captures the use case of wanting to restrict folks from adding/removing issues from the active sprint. Is there a way to restrict users from editing the 'sprint' field? will this be honored in situations where users can drag and drop or right-click to move stories in or out of sprints?

             

            Charles Fisher added a comment - It doesn't seem that the description of this issue captures the use case of wanting to restrict folks from adding/removing issues from the active sprint. Is there a way to restrict users from editing the 'sprint' field? will this be honored in situations where users can drag and drop or right-click to move stories in or out of sprints?  

            SteveK added a comment -

            Agreed with Davin, permissions should exist to list project sprints to a user based on a user's project permissions. Currently any user with edit jira permissions can view all sprints across our jira instance in the sprint lookup/dropdown.

            SteveK added a comment - Agreed with Davin, permissions should exist to list project sprints to a user based on a user's project permissions. Currently any user with edit jira permissions can view all sprints across our jira instance in the sprint lookup/dropdown.

            I can't have people changing scope in a sprint, nor can I remove their ability to edit an issue. These need to be separate. Thanks!

            Davin Hoekstra added a comment - I can't have people changing scope in a sprint, nor can I remove their ability to edit an issue. These need to be separate. Thanks!

              Unassigned Unassigned
              jalbion Janet Albion (Inactive)
              Votes:
              44 Vote for this issue
              Watchers:
              32 Start watching this issue

                Created:
                Updated: