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

[Tracked in Issue Links] various tickets regarding confusion around sprints functionality

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Backlog - Sprints
    • None
    • 7
    • 11

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

      See linked issues

          Form Name

            [JRACLOUD-90822] [Tracked in Issue Links] various tickets regarding confusion around sprints functionality

            David Pezet added a comment -

            23ef3e30d63c Could this also be related to JRACLOUD-82356? I agree with f904f5e6dbfc. Since defaulting to not include Manage Sprint permissions breaks existing boards; and allowing the Manage Sprints permission on projects that don't use sprints, doesn't affect the project (since it doesn't use sprints anyways) this should be a bug. I believe whether Sprints are applicable should be Team/board specific, not project specific. A rogue team managed project can break company managed project boards.

            David Pezet added a comment - 23ef3e30d63c Could this also be related to JRACLOUD-82356 ? I agree with f904f5e6dbfc . Since defaulting to not include Manage Sprint permissions breaks existing boards; and allowing the Manage Sprints permission on projects that don't use sprints, doesn't affect the project (since it doesn't use sprints anyways) this should be a bug. I believe whether Sprints are applicable should be Team/board specific, not project specific. A rogue team managed project can break company managed project boards.

            Andrei Tuch added a comment -

            Adding a usecase from real life: we have Scrum Boards that include issues from multiple projects. A user must have Manage Sprints permissions in all of the in-scope projects, or they won't see Start Sprint / Complete Sprint buttons, even for sprints with issues from only one project.

            The edge case is that this includes JSM projects. If a JSM project (in our case, a release management tracking project) is included in the filter query, then any sprint manager in that Scrum Board requires Manage Sprint permissions even in the JSM project, which cannot possibly have Sprints!

            See CES-42582 for details.

            Andrei Tuch added a comment - Adding a usecase from real life: we have Scrum Boards that include issues from multiple projects. A user must have Manage Sprints permissions in all of the in-scope projects, or they won't see Start Sprint / Complete Sprint buttons, even for sprints with issues from only one project. The edge case is that  this includes JSM projects . If a JSM project (in our case, a release management tracking project) is included in the filter query, then any sprint manager in that Scrum Board requires Manage Sprint permissions even in the JSM project, which cannot possibly have Sprints! See CES-42582 for details.

              Unassigned Unassigned
              23ef3e30d63c Anusha Rutnam
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: