nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Have two boards with different sprints linked to eachother

Support_53u4yq

I have two teams, one that specifies what needs to be done from issues that our users provide, and one that actually develops the new functions. We would like to have two different boards for the two of them. The team that specifies should have a continuous board without time limit, and the developers should have one with sprints. Is there a way to get that set up working?

Further on we would like to link the "done" section in the specification board to the "backlog" of the developers board so that when a new function is specified it will automatically appear in the developers backlog to be included in the next sprint.

Accepted answers

All comments

Alexey Matveev

Hello,

You can create a Kanban board for continuous board. When you create this board, provide a filter, which chooses required issues.

For the developer team you can create a scrum board with a filter, which would choose only issues in the required statuses.

I guess it would do the trick.

Tarun Sapra

Hello @Support

What you require is easily doable in Jira and can be implemented very nicely. Basically have a single workflow for the features and make sure first few steps of the workflow decide "what needs to be done" and the second part of the workflow comes into play if the Scrum team actually works on the ticket.

So now, you have one workflow and based on the workflow you can create 2 boards, first Kanban board (continuous board) and second Scrum board for dev team. Make sure the status in the right most column of the Kanban board makes up for the left-most column of the Scrum board such that when approving team says "done" on kanban board then the issue automatically goes in the first column of scrum board.

Also you can have an "obsolete/cancelled" status which the "approving" team can use and thus if they feel that the issue needs not to go for development then they can directly move the issue to cancel status instead of to the scrum board.

Support_53u4yq

Hi! @Tarun Sapra

I'm sorry for asking stupid questions, I'm a complete beginner in Jira! Could you possibly provide some more details on how to create the workflow that you're describing in your answer?

Further on I would prefer that when a thing says "done" in the kanban board it should appear in the "backlog" of the scrum board and not in the first column. Is that possible?

Thanks for helping out!

I'm a complete beginner using Jira, so I'm sorry for asking some stupid questions!

Could you possibly provide me some more details on how to set up the workflow you're describing in your answer?

Further on I would like the "done" section on the Kanban board to link to the backlog, not to the first section of the scrum board. Is that possible?

Thanks for helping out!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud