-
Suggestion
-
Resolution: Fixed
-
None
-
8
-
7
-
-
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.
- is duplicated by
-
- Closed
- relates to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-5410] Ability to have one sprint active per Agile board even if they are in the same project
| Workflow | Original: JAC Suggestion Workflow [ 3066042 ] | New: JAC Suggestion Workflow 3 [ 3656871 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2627059 ] | New: JAC Suggestion Workflow [ 3066042 ] |
| Current Status |
Original:
{panel:title=Atlassian Status as at 27 January 2016| borderStyle=solid| borderColor=#cccccc| titleBGColor=#dddddd| bgColor=#ffffff}
Please see [comment below|https://jira.atlassian.com/browse/GHS-5410?focusedCommentId=859656&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-859656] Kind regards, Martin JIRA Software h3.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|https://confluence.atlassian.com/jirasoftwarecloud/jira-software-labs-764478187.html] 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. {panel} |
New:
{panel:title=Atlassian Update – 25 April 2018|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ffffff}
Hi everyone, Parallel Sprints are no longer a Labs feature and were shipped with Jira Software 7.1 release. You can now enable the capability in Jira Software configuration. Read more in Jira Software 7.1 [release notes|https://confluence.atlassian.com/jirasoftware/jira-software-7-1-x-release-notes-788728210.html#JIRASoftware7.1.xreleasenotes-parallelsprints]. Cheers, Katarzyna Derenda Product Manager, Jira Server {panel} |
| Fix Version/s | New: 7.1.0 [ 59897 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Resolved [ 5 ] |
| Support reference count | New: 7 | |
| UIS | New: 8 |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2317993 ] | New: Confluence Workflow - Public Facing v4 [ 2627059 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2038797 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2317993 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2027237 ] | New: JIRA PM Feature Request Workflow v2 [ 2038797 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 737498 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2027237 ] |
| Labels | Original: sw-c triaged | New: affects-server sw-c triaged |