Is it possible to have two kanban boards in for a project, each with a burndown, that are related?

I am customizing Jira to my Company's workflow and I am very amazed by it.

A requirement came up today, and I hope there is a way I can represent it on Jira:

We have a project and I would like to have two boards for it: a development board and a testing board.

I would have issues that I would create and they would start on dev board's TO-DO column. Once the issue is marked as "DONE", it would move to the test board.

Is this possible to do?

This requirement arrived because I created one board with development and testing columns, but the problem is that I want to have a burndown related solely to development tasks (I want to measure my development velocity). We have a workaround at the moment that, once the dev finishes that tasks and commits it, he marks the remaining points as 0. But this is somehow awkward.

Is it possible to do what I want?

Or do you see any improvements on our process that we could make?

thanks!

2 answers

1 accepted

I think it may be possible by putting the search and the filters right.

You can set up multiple boards for the same project, since a board is just a visualization of a search term. Lets make an example:

You want to have these statusses in the development board: open, in progress, done

and the same in the testing board. So you can set up a flag, lets call it "test" in a new custom field, or create the statusses open, in progess, done, test open, test in progress, test done

Now you put the search terms for the board according to the flag or the statusses using the "Work Sub-Filter"

In the workflow it is possible to "move" issues from board to board by setting the status or setting the flag accordingly.

We are using a similar way to use two Sprint boards across a dozen projects filtering the tasks by the labels "frontend" and "backend"

Maybe this will work for you, too.

GREAT!!! This is exactly what I need!! THanks!

0 vote
Joe Pitt Community Champion Jun 15, 2014

I don't think you can have two boards. Another work around is to have 2 projects and MOVE the issue. However, that introduces other issues, the most basic of which is the issue ID would change.

Ok, I understand. I will think about how to change our process so it suits JIRA better :)

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,315 views 14 20
Join discussion

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