How to configure two boards in one project?

[Ayendra_Gunasekara]

Hi. I'm trying to create another board where I can manage the requirements. Basically the existing board includes,

Board 2 (Existing board)

Backlog - In progress - Dev completed - In QA - QA completed - Review - Done

I need a board to manage the requirement prior to adding the issue into the existing boards backlog, which includes,

Board 1

To Do - In progress - Review - Done

And once the the issue is moved to the Done column in board 1, I want that to be displayed in the backlog of board 2

I'm trying a to create and configure board one. Please let me know how best this could be done.

Thanks,

[Petter Gonçalves]

Hello @Ayendra_Gunasekara

Welcome to the Atlassian Community!

Per your description, I understand you would like to track the progress of your issues using two boards in your projects.

Can you confirm if you are using a next-gen or Classic project?

It's not possible to create multiple boards for a Next-gen project board, however, you can achieve the goal you want in a Classic project board. Please, allow me to bring you some concepts about boards and how it works to make sure we are on the same page here:

Jira boards basically represent the workflow of your Jira issues, so you must map the workflow statuses to board columns in Jira Classic projects. To achieve the scenario you want, you can create another board and map your issue statuses in a way you can track your issue progress prior to the next board, you just need to add statuses in your workflow to track those previous steps.

Another thing you must have in mind is that all Jira Agile reports consider an issue to be resolved when it is in a status that has been mapped to the right-most column of your board, added with a valid resolution and a status in the Done category, so the reports related to the first boards might not display a correct data if you will not resolve them at the board. That being said, if you want to track both boards with reports, I suggest using two different issues to track in both boards, instead of using the same issue to map all the progress from one board to the other. Explaining better:

1. You would use different issue types and workflows to map the progress of each board.
2. Then, use the Issue Link feature to set the relation between both issues, to know they are related to the same scope.

Let us know if you have any questions.