Sub tasks appears in "Issues without epics" swimlane

[Jacek Trossen]

Hi at all, 

we have a very simple Kanban board in our Jira. For this board we use swimlanes based on Epics. 

If we create stories, tasks and sub task from the epic all these tasks will be displayed correctly in the board under the swimlane. Also if we use the default filters (by user). 

However, we create a new story or a task and then convert it into a sub task, which will be related to a story or task, which has a epic link. The sub task is displayed in the Kanban board in the corresponding swimlane. So far so good, if we now apply a filter (by user) this sub task no longer appears in the swimlane (epic) but in the swimlane "Issues without epics"

You can't assing a epic link to a sub task, so how to fix the display for sub tasks?

[Trudy Claspill]

Hello @Jacek Trossen 

Welcome to the Atlassian community!

Can you tell us are you using a Company Managed project or a Team Managed project? That information will be shown at the bottom of the navigation pane on the left.

[Jacek Trossen]

It is a Company-managed project. 

[Trudy Claspill]

So far I have not been able to replicate this.

Can you provide images from your system that show 

- the board after you've first created the subtask

- the board after you convert the subtask to another issue type

- the board after you activate the filter. Is that filter for Assignee activated using the Assignee avatars, or are you using a Quick Filter?

[Jacek Trossen]

Yes sure. In creating these images, I found a simpler pattern to reproduce this behavior. It is also reproducible in a Team Managed project.

I created a demo epic "DemoEpic" with one story "Parent issue" and a sub task "Subtask from Story" as a child from the story, see the following image. 

The story is unassigned and the sub task is assigned to me. Now when I apply the filter the task appears in the swimlane "Issues without epics". This also happens when the parent ticket (story) has been assigned to someone else. See next image.

If the parent ticket is also assigned to me, then the sub task appears in the correct swimlane "DemoEpic". See next image.

It has something to do with the parent ticket.

[Trudy Claspill]

Thank you for that additional information.

When I follow your steps and set the Assignee as you specified, then the problem does occur for me also.

In your original post you talked about converting the subtask to another issue type, but you did not include that in the detailed steps above. Is this a problem only for the subtask when it is a subtask, or also if you convert the subtask to a standard issue type?

[Jacek Trossen]

Thanks for the information it is reassuring that the problem is also reproducible elsewhere. 

No I have not include the details to the original post. From the present point of view the conversion into a subtask has nothing to do with it this came from my first observation of this problem. 

Now I am pretty sure that the problem always occurs when it is a subtask and the parent ticket is unassigned or assigned to another user.

What is the possibility to fix this? 

The workarounds would be:

1. use Task instead Subtask or
2. assign the same user to the parent ticket.

Both workarounds do not fit our workflow.

[Trudy Claspill]

At this point I advise that if you are on a paid subscription you have a Jira Administrator open a case directly with Atlassian Support to find out if this is a known issue for which they have a work-around, or if it is an issue they were unaware of, or if it is intended functionality.

https://support.atlassian.com/contact/#/

[Jacek Trossen]

Thank you very much for your support. I will contact our admin.

[Mesa Admin]

Hello,
We are observing the same issue where a Sub-task of an unassigned story or of a story assigned to a different user appears in "Issues without Epic" swimlane.

Were you able to find a solution to this issue?

Thanks

[Jacek Trossen]

Hi,

no, I am be not able to find a solution. This is a known issue https://jira.atlassian.com/browse/JSWCLOUD-16752

You can vote for it and it might get fixed sooner.