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

[oscar albrecht]

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!

[Dennis · Accepted solution]

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.

[oscar albrecht]

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

[Joe Pitt]

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.

[oscar albrecht]

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

[Sapna Sharma]

Issue are still migrated to another board after changing the issue id.