Acceptance Criteria

• The supported setup is
  • a "Scrum of Scrum" Board with a filter query that can span multiple projects, and
  • a separate board for every team.
  • How the JQL could look to make the team-specific distinction is unclear. (currently, this could be done with a label; something more dedicated to a team would be nicer)
• The rapid board (SoS and for every team) shows an active sprint as soon as its filter selects an issue that is currently in a sprint
  • Note: this is currently working
• In the sprint planning, the teams can pull the stories that they think they can complete in that sprint. These stories will automatically be manipulated to match the JQL so that it will show up in the team's specific board.
  • Note: Manually, this is also sorts of working. By pressing "l" I can quickly label an issue with "team-alpha", "team-beta", etc.); A more automated and/or team-oriented way would be nice
• Sub-tasks for the user stories that a team selected will show up in the team specific board (related to GHS-5301).
  • Note: This is the only part that is currently lacking. The options I am currently aware of both involve extra plugins:
    1. Auto-Inherit the labels from it's parent
    2. Extend the JQL so that I can query for parent issues. For example: ... OR parent(labels = team-alpha) ...

This Story is somewhat related to GHS-5542, but with a common Sprint defined for all teams, you gain a more concise reporting and task boards. (I hope...) Also GHS-5410 is similar to this request, as I understand GHS-5410 it is created under the assumption, that you create two different sprints in two different boards in the same project, while this user stores suggest to have a common sprint that works over several boards.

Sprint Planning Flow

• Plan the new Sprint in the "Scrum of Scrums" Board
  • Select User Stories for all teams, include them in the next upcoming sprint
  • Assign the User Stories to a team (label them, or do whatever is necessary)
• Do the second part of the Sprint Planning in the Team Specific board. Create Subtasks for all User-Stories
• When all the Sprint Planning is done, start the Sprint in the SoS Board.