Is there somewhere we can vote on this? We have multiple teams and when one sprint is closed, it rolls to another unrelated sprint. Maybe if we can also categorize sprints, the associated stories will fall into the category in which it's already located when the prior sprint is closed. I'm pretty surprised that this isn't a bigger problem with Atlassian since some of your clients have thousands of employees and have multiple and interrelated projects.
Vote on what precisely?
JIRA Software already does parallel sprints, see https://confluence.atlassian.com/jirakb/multiple-active-sprints-in-agile-scrum-board-when-the-parallel-sprint-option-is-disabled-779158592.html and https://confluence.atlassian.com/agile/jira-agile-administrator-s-guide/jira-agile-labs#JIRAAgileLabs-BlueFROMJIRAAGILE6.0.3ParallelSprints - then probably add to what they have to say (I'm actually sure you have additional questions here, but I'm not sure where they're already answered in the first doc)
Hmm. From memory, the version of JIRA you are on (6.4.11) supports a version of JIRA Agile where the parallel-sprint stuff is available, albeit as a JIRA Lab (it's safe to assume it's not going away though, unlike some other lab stuff). What's the Agile version?
Agile version is 6.7.12. Yeah, we can run the parallel sprints but we have some clunkiness to closing them. Like I said, stories in a sprint from one team project will end up on another team projects sprints when their sprint is closed. I know the active stories look for a new sprint when the one they're in is closed but when it goes to another team's sprints...
That's our dilemma and I don't know if a different version of JIRA or Agile will eliminate that issue.
Thank you Nic.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG