Multiple RapidBoards

I just created a sample project and two sample rapid boards. Both rapid boards are pointing to the same project. The idea was to simulate multiple scrum teams working on a common product.

Both boards looked at the same backlog (same project) and one started a new sprint. Much to my surprise, the other rapid board was now sharing the same sprint!!

What does a rapid board accociate its data with? A filter? A project? Itself? Now both rapid boards are saying they are in progress... on the same sprint???. Hopefully I am missing something, otherwise there can only be one rapid board per Jira server.

Each rapid board has its own filter, but the criteria is identical. Are the boards associated with a filter criteria?

Jira 5.0.4 and Greenhopper 5.10.1

3 answers

1 accepted

The Rapid Board simply selects the issues that are included by the filter and works the rest out from there. In this case the issues happen to include an active Sprint so the Rapid Board displays the information about that active Sprint.

Both boards are in progress because they both include issues that are in a Sprint. A board can include issues that are in multiple Sprints in which case it will show all of those Sprints (i.e. Scrum of Scrums)

If you define filter criteria that selects different issues across the two boards they will operate completely independently.

Thanks,
Shaun

I had the same issue, and could not understand why on earth I got the other sprints, issues, etc. when the filter was obviously correct... until I understood that there is a difference between Quick filters and Board filter...

Is it possible to have a type of sub-task in one RapidBoard/Sprint while the parent task would remain in another?

Trying to do this:

- once we're done with the work, we want to add a sub-task to indicate that documentation needs updating

- I created a new type of sub-task (Documentation)

- I created a new Rapid Board which only shows those Documenattion subtasks

- But when I create one, it automatically gets assigned to the sprint that the parent story belongs to and I could not find a way of putting just the sub-talk back into the back log

Ideally I would want documentation tasks to run in their own sprint, I presume it's because they are sub tasks, not full blown issues...

Or any advice on how to handle this kind of thing?

You can't have a subtask in a sprint without it's parent story.

I'd suggest just creating a separate story for the documentation and linking it to the feature story.

Thanks,
Shaun

Is it possible to have a type of sub-task in one RapidBoard/Sprint while the parent task would remain in another?

Trying to do this:

- once we're done with the work, we want to add a sub-task to indicate that documentation needs updating

- I created a new type of sub-task (Documentation)

- I created a new Rapid Board which only shows those Documenattion subtasks

- But when I create one, it automatically gets assigned to the sprint that the parent story belongs to and I could not find a way of putting just the sub-talk back into the back log

Ideally I would want documentation tasks to run in their own sprint, I presume it's because they are sub tasks, not full blown issues...

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

262 views 0 12
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot