Updating and Organizing Project Boards

[Rachel O_Loughlin]

I'm reviewing and organizing a project that, in the past, has had multiple devs and project managers working on it. There are three boards tied to it - two kanban and one scrum. Not all, but some issues are duplicated in the backlog of two different boards. I'm confused about where to start with organizing, removing duplicate tasks, etc. so the team can create a clear roadmap of work to be done.

Workflow management is typically kanban style for this project with a few sprints throughout the year. Do I start by moving issues on one board and delete the other board once migrated?

[Trudy Claspill]

Hello @Rachel O_Loughlin 

Welcome to the Atlassian community!

When you say the issues are duplicated do you mean there are two issues with different issue keys but the same content? Or do you mean one issues is shown on more than one board?

Boards display issues based on a filter. An issue can be within the results of multiple filters so an issue could show on multiple boards at the same time.

If that is the case for you, then you will not be "moving" issues. It might be the case that you just need to change the board filters.

Can you share with us the Filter details for each board?

[Rachel O_Loughlin]

Thank you for the explanation and for your patience! I still have a lot to learn within Jira.

Confirming it's the same issue appearing on more than one board. The Filter details are noted below for each board.

Board 1 (Kanban): project = YCL ORDER BY Rank ASC

Board 2 (Kanban): project = "Youth Coding League" AND issuetype = Epic ORDER BY Rank ASC

Board 3 (Scrum): project = YCL ORDER BY Rank ASC

[Trudy Claspill]

The good news is that all these boards refer to the same project. There is no need to "move" issues.

And it is perfectly acceptable to have both Kanban and Scrum boards referencing the same project/issues.

I am curious about the management of work being mostly kanban with a few sprints throughout the year. What is the reasoning behind that? What problem is being solved with that hybrid approach?

How is that actually implemented? Does the team stop working in the kanban manner during the sprints? Is it only part of the team working on the sprints while the rest continues with kanban? 

What are your goals with your reorganization efforts? What problem(s) are you trying to solve with this effort? How is the current organization not working for you?

Until we know your problems/goals, it is difficult to provide meaningful advice.