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

Ability to have one sprint active per Agile board even if they are in the same project

XMLWordPrintable

    • 4
    • 11
    • Hide
      Atlassian Status as at 27 January 2016

      Please see comment below

      Kind regards,
      Martin
      JIRA Software

      Additional information

      At the moment, our recommended configuration for multiple teams working off the same backlog is to have separate boards for each team (using mutually exclusive filters such as "project = x and component = TeamA" and "project = x and component = TeamB") then a parent board that includes all of the issues in the child boards (with a filter such as "project = x"). In this configuration the two children boards can rank and execute sprints completely independently while the parent board will see all of the sprint information from the sub boards.

      However, we do understand the need for multiple teams to be able to work from a single board. In the future we would like to address this by providing a team concept so that sprints and issues can be marked with a particular team. However, in the mean time we have implemented the ability to have multiple sprints active on a single board by enabling the parallel sprints feature. When the feature is enabled multiple sprints can be started on the same board, the sprints can be filtered easily on work mode and you can choose which sprint to finish when closing out a sprint.

      Show
      Atlassian Status as at 27 January 2016 Please see comment below Kind regards, Martin JIRA Software Additional information At the moment, our recommended configuration for multiple teams working off the same backlog is to have separate boards for each team (using mutually exclusive filters such as "project = x and component = TeamA" and "project = x and component = TeamB") then a parent board that includes all of the issues in the child boards (with a filter such as "project = x"). In this configuration the two children boards can rank and execute sprints completely independently while the parent board will see all of the sprint information from the sub boards. However, we do understand the need for multiple teams to be able to work from a single board. In the future we would like to address this by providing a team concept so that sprints and issues can be marked with a particular team. However, in the mean time we have implemented the ability to have multiple sprints active on a single board by enabling the parallel sprints feature. When the feature is enabled multiple sprints can be started on the same board, the sprints can be filtered easily on work mode and you can choose which sprint to finish when closing out a sprint.
    • 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.

      Our development teams are separated into pods. Each of these pods are working on a different release simultaneously. The limitation that you can only have one sprint active per project limits the use of rapid board for our teams.

              Unassigned Unassigned
              d042d064de91 Micah Figone
              Votes:
              186 Vote for this issue
              Watchers:
              119 Start watching this issue

                Created:
                Updated: