Migrated project issues not appearing on board despite mapped workflow

[David Powell]

Hi there,

This is a common problem but the other tickets did not have a solution that has worked.

I created a new team-managed project with a simple Kanban setup and created a very basic workflow which was then mapped to columns on the board. New issues were not showing up on the board, but after I played around I managed to get it to work somehow.

I have now moved a few hundred issues into my project from another company-managed project, and around 2/3 of them do not appear on the Kanban board. They are visible in Issues and List. I have:

• Tried enabling the backlog and checking to see if the issues were there. They are not.
• Set up a custom filter to show all tickets, which did not change the problem with it off or on.
• Adjusted the status on multiple issues to see if it somehow snapped them into the workflow. This did not work.

Here are some of the columns in the Kanban config screen:

Here are the column headers from the live board:

Clearly *something* is filtering the issues from the Kanban board. The template I'm using has fairly limited options for configuring the Kanban board and so I can't find anything in the options that could potentially restrict these issues from showing up.

[Trudy Claspill · Accepted solution]

Hello @David Powell 

Welcome to the Atlassian community.

Can you confirm for us that this concerns a Software project, both as the source and destination?

What are the statuses assigned to the missing issues?

What are the issue types of the missing issues?

Do you have anything set for the Group By option in the Team Managed project Kanban board?

[David Powell]

Hi Trudy,

Thank you very much. Well your questions have already helped me troubleshoot but I'll answer all in kind and let you know my situation now:

1. Both are software projects
2. The statuses were of any types
3. All the missing issues are subtasks, I just discovered this answering your questions
4. No

So it appears that all of the missing issues are subtasks. Edit: Nevermind I can convert tasks to subtasks.

Perhaps these two problems are linked? Is there something in how I set up the project?

[Trudy Claspill]

Subtasks don't display as cards on a Team Managed project board unless you set the Group By option to Subtask.

I'm not seeing the Convert to Sub-task option directly in the issue details view Action menu, but I do see it in the Action menu available from the View All Issues screen.

This is noted in the unresolved Suggestion here:

https://jira.atlassian.com/browse/JRACLOUD-83176

[David Powell]

Thank you!

So my vision for this project is the majority of work would be done at the subtask level and tracked by a supervisor on the board, each subtask being under a story and then an epic.

It sounds like it would be better to have all of this work set up as tasks or stories rather than subtasks if we want to rely on the Kanban board to track it. Correct?

[Trudy Claspill]

The answer is "it depends".

Subtasks are an integral part of the parent issue under which they reside. Generally the "deliverable element" is defined at the Task level and subtasks are used just to break down the work to a finer level of granularity for assignment to separate individuals, for more detailed estimating and time tracking, or because there is a need to track more details at a more granular level.

On the board you can have swimlanes by Epic, in which case the Tasks will display as cards but the subtasks will not. Or if you choose to have the swimlanes by Assignee, likewise the Tasks will display as cards but not the subtasks, and the Assignee swimlanes will be based on the assignee of the parent issue. Or you can have the swimlanes by Subtask in which case the Subtasks will display as cards but the parent Tasks will not. 

What type of visualization do you want from your board?

What type of reporting would you want to get concerning the information?

[David Powell]

I think with all this information I can consider this resolved.

The reporting requirements right now are loose as what I'm working towards is setting up a Kanban board which tracks all of the team's work with some specified categories. The three-layer-deep hierarchy I was thinking of isn't strictly necessary and working with epic-task with optional subtasks seems in keeping with the point of the software and will serve us fine.