Absolutely, this works today. The board decides what sprints exist based on the sprints that are attached to the issues included in the board's filter. For example, if you have two boards with the same filter they will see the same sprints but can be configured with different swimlanes, filters etc.
Absolutely, a board discovers which sprints exist by looking for all the issues that match the board's filter then looking at the sprint field. If board A includes issues that are in a sprint also shown on a board B then the sprint will be shown on both A and B.
The only exception to this is 'future sprints', these are just points in the backlog at the moment (they don't actually own any issues or change the sprint field). We'd like to change this in the future.
Is there a JIRA in the Atlassian JIRA for changing the following?
"The only exception to this is 'future sprints', these are just points in the backlog at the moment (they don't actually own any issues or change the sprint field). We'd like to change this in the future."
Does this mean sprints created on one board that aren't currently active won't show up on another board with the same filter? This is what I need - so I can have one board that shows everything (active and future sprints) for the project, and then boards for each individual scrum that show only their active and future sprints.
@Anna Kinasiewicz @eric lin I think I found a way you can share future sprints across boards. We have a "Sprint Planner" scrum board which includes all sprints (including future) and all Teams. We also created a Team field in JIRA to match AR by using this tutorial - https://www.youtube.com/watch?v=lE2HIZpJKxg&feature=emb_logo
Then we created separate Scrum boards for each team. If you go back to your master board, and assign a task into a future sprint AND assign the team - when you go to the team specific board, the future sprint will show up and be shared. You can then add any other tasks in the board to that future sprint.
For our set up, that worked, hope it helps.
If you working on the same backlog, it seems to be possible with parallel sprints in GH 6.0.3:
However, it still undergo development and may be further change or tweak in future release. You need to enable it in greenhopper labs to start testing it:
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events