Issues without epics - kanban board

[Maggie Spitchka]

I have a few subtasks that sit under a section called "issues without epics" on my kanban board. They are tied to a story that has an epic, so I'm a little confused. The ability to assign them to a sprint / move the sprint is also not possible?

Their parent stories are in a variety of statuses (1 - done, 1 - hold, 1 in done but the subtask also in done? so not sure why showing there)?

[Paul Reich]

While I may not have solved this, I believe I've uncovered the source of the issue (or at least part of it).

I am experiencing a similar issue (referring also to the resolved community above where I have my board configured using Epics as Swim lanes).

---

I have experienced this before, but wasn't certain of the origin:

At the bottom of my board was a section "Issues without Epic" containing 5 issues.

I have just created two new Epics in sequence, each with 1 parent Task so far - each time I created the parent Task within the Epic, the count under the "Issues without Epic" section increased by 1, currently totalling 7.

---

Even stranger is when I removed the parent Task from the Epic i.e. now both the Epic and the Task are under the same Sprint separately, the board appears to include the Epic itself in the count of "Issues without Epic" - most peculiar.

---

I then moved both the separate Epic and Task to a different Sprint and the count reduced by 2.

---

Current perplexing conclusion:

The "Issues without Epic" appear to be Epics themselves, which explains why the "issues" are not visible.

[Trudy Claspill]

Hello @Maggie Spitchka 

The ability to assign them [subtasks] to a sprint / move the sprint is also not possible?

That is correct. You can't assign subtasks to a sprint independently from their parent issue. Sprint velocity/capacity/planning happens at the parent issue level, not the subtask level. All subtasks will inherit the Sprint value from their parent issue.

You also don't assign anything to a Sprint when you are using Kanban. Sprints are applicable only when using a Scrum board.

Can you show us your board these subtasks in the section called "issues without epics"? Is this board for a Company Managed project or a Team Managed project? Do you have a Swimlane setting (if Company Managed) or a Group By setting (if Team Managed) on this board?

[Maggie Spitchka]

Its a company-managed project... we have a broader kanban board, and then we sprint plan from there. I realize this may be counterintuitive but one was created before other and I'm not entirely sure what the process of changing the kanban to scrum board would be since everything already exists on there and we're able to workplan via the sprints. 

So what exactly does issues without epics mean? Their parent issue has an epic that its created off of, so just not sure what they're doing in this category especially for the example that the subtask and parent issue are both completed 

[Trudy Claspill]

Can you provide an image of the board showing the sub-tasks in the group labled "issues without epics"?

Have you set the Swimlanes on this board to be Epics?

I found a few other posts on this same topic:

https://community.atlassian.com/t5/Jira-questions/Sub-Tasks-listed-in-Issues-without-Epics-when-Parent-task-story/qaq-p/1505579

In this case the parent story had been removed from the sprints.

In a response on that post another user noted that there is a related Atlassian issue that this occurs if the subtasks are under a custom standard issue type.

https://jira.atlassian.com/browse/JSWCLOUD-16752

https://community.atlassian.com/t5/Jira-questions/Sub-Task-incorrectly-under-quot-Issues-without-epics-quot/qaq-p/1811944

In this post it was related to the use of an Assignee filter at the same time.

[Maggie Trychel]

One of them said to delete the epic off the parent and re-add, worked for all but 1. I'll take it but helpful to definitely log this is still an issue. 

Pics below before the changes since we were talking about kanban vs. scrum board and how mine is set up (swimlanes are driven by status, then epics categorize into groupings)