Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can I create a Kanban board and a Scrum board in the same project with different tickets?

Justin Ellis
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 8, 2020

I am working with an external team to create and validate user stories but an internal team once those stories are validated and ready for dev. I want to use a Kanban board to create and validate the user stories, and once they have passed all of the validation steps, transition those tickets over into the Scrum board for my dev team to begin working on. Ideally, these two boards would have completely separate backlogs and completely separate tickets. 

When I create a new Kanban board in the existing project, it duplicates over all of the tickets from the backlog and other sprints onto the Kanban board. Like I said above, I don't want tickets from one board on the other, so I don't know if using filters is the right solution.

Does anyone know how to create two separate boards in the same project? 

1 answer

1 accepted

0 votes
Answer accepted
Jack Brickey
Community Champion
April 8, 2020

Hi Justin, welcome to the Community!

Yes you absolutely can create multiple boards for a given project and/or multiple projects. Boards are just visual filters of issues with some fancy features, e.g. drag and drop, swimlanes, etc. If you don't want your boards to overlap you simply need to ensure that the filters that define the boards don't overlap. To help you definitively I would need more info about your situation. What issues do you want to see on each board and how are they uniquely defined. For example, maybe statuses can be used, or Components, label, custom field etc.

Justin Ellis
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 8, 2020

Hey Jack,

Thanks for the response! I'm still learning all the ins and outs of Jira, so forgive me if this is a very basic issue. Seems like using statuses was exactly what I needed to do. Thank you again!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events