We are also experiencing this issue still. We are currently on Jira cloud. 

30f1479b99b8 and fe99f810edec can you please create a Support Ticket with us so we can investigate? Please reference this bug (https://jira.atlassian.com/browse/JSWCLOUD-16752) in your ticket. Thank you!

The Bug is closed but I am still facing this particular issue. Can anyone help me resolve this?

Same issue here, with enhanced backlog and board enabled. The tasks are identical to others (Epic>Task>Subtask) but for some reason show in the "issue without epics" lane at the bottom. 

Hi everyone who has commented recently - can you please create Support Tickets with us so we can investigate further? If you are admins on multiple sites, make sure to create the ticket in association with the site on which you continue to see this behaviour. Thank you.

Hi ! We enabled the new experience (it's nice), and still we are facing this issue.

Even with activated "Enhance my board and backlog", it still exists.

Sub-tasks are showing as "Issues without Epic" even if the parent task contains Epic.

Is there any solution? Workaround?

P.S. It works fine if the parent of the sub-task is assigned to the same user and a sub-task. But it would not fit our workflow.

We still have this issue. It may solve it in the new board (TBD) but is not fixing the core issue since Structure still shows some stories as "No Epic" even if they have one.

Hi

If I take the steps as described it works fine on the new enhanced board, if you still use the old board style the sub-task will still show as an issue without an Epic

You need to switch to the new Enhanced board

we are using company managed and continue to see the issue. 

It appears to have worked for my board, but the "Issues without epic" row still says there are issues, even though none are shown.

It appears to be fixed for us.  I wonder if the issue for those that are not seeing it fixed is the Company-managed vs. Team-managed projects.

agreed, this UI change looks good - however it does not fix the issue of child issues of stories on the board being grouped under "missing epics" / "issues without epics" 

@Eoin I still have the issue with enhanced board and backlog. The issue is not resolved.

Hi all! Users can now turn on the new UI which resolves this bug https://community.atlassian.com/t5/Jira-Software-articles/Enhanced-Jira-board-and-backlog/ba-p/2331946 I am going to close this ticket - but let me know if you are still having problems with this on the new UI.
Thanks

Open since 20181? any resolution updates, investigations one can share please?

also experiencing this issue

Also experiencing this on one project with an automation to copy the epic link. Other projects with similar automations are working.

This issue will be resolved by UIF. Have downgraded the bug to `Medium priority` to avoid an SLO breach as we are not going to address the bug directly.

Still a bug - Unbelievable, that this is still an issue since 5 years!!!!

I am experiencing the same bug on one of my project's boards as well.

Juts registering we've got this bug too.

Created on 05/Apr/2018 and still not fixed? Absolutely annoying...

@Kurt: Thanks, will try that work-around as well. At least one person who's working on a solution!

This issue also impacts our workflows.

One workaround that works some/most of the time, is to remove and then re-add the Epic link to the parent of the Sub-Task. Seems to not always work, but most of the time. Unfortunately, this seems to often be temporary, and issues again start showing up as 'without Epic'. But perhaps is useful as a method of resolving the overall bug.

Ideally, this should be resolved so that a work-around is not required.

This same issue has been resolved for the server version here JSWSERVER-10683

Why is this still "gathering" information when the impact is known and being resolved on server already.

when will this be resolved?

Hi all, I'm working with Kanban teams mainly and it's really confusing during our daily scrum not to have a solution on this one.

The subtasks shall be aligned with their parent tasks and if not present (for any reason like being filtered out), then they should pick up their parent's Epic.

Please get this fixed, the functionality of swimlanes by Epics is useless without it. 

We use swimlanes by Epic across most of our projects and this is a poor experience. 

This bug causes a lot of pain and it means that configuring Swimlanes by Epics is a very poor experience. It surely can't take that much effort to infer that the subtasks also belong the epic that their parent ticket belongs to? 🤷‍♂️

I can only concur. When using subtasks as a way of working with Story breakdown into implementation issues, this is a must. Going through the board during standup, filtering on each team member in turn, erroneously moves subtask issues to the "Issues without Epics", since the product owner has ownership and hence is assigned the Story. The structure is still valid: the subtask still belongs to a Story in an Epic... 
This is a non-logical flaw which makes the use of subtasks ... unusable.

Please fix.

Without the fix, the functionality of swimlanes by epics is useless. And the fact that this has not been addressed for so long concerns me a lot.

how long ever will we wait for you to fix the bug?

If users are complaining for 4 years and there is no one there to hear it do they make a sound?

Is there any information, if this issue will be ever fixed? The linked bug policy states that this ticket status "Gathering impact" means

"This issue has been reviewed, but needs more supporting information to gauge the pervasiveness of the problem"

It's been +4 years that this issue has been reported. So what kind of "more supporting information" is needed? I think we as users are more than happy to help you. Feel free to reach out.

Best regards

This is a daily issue for my team. We are a small team dealing with many epics in every sprint and we are often confused when looking at our stories and tasks and always wondering to which epic they are related. 

Nice functionality but confusing without this simple fix.

Please fix

this makes it impossible to manage stories with subtasks......please fix

Unfortunately, this has been outstanding for years, but classified as low priority. So, I assume it is unlikely to get fixed any time soon.

Perhaps if enough people put the issue on watch the priority will get bumped up?

Tim Hubbard

You have such amazing functionality, surely this should have a fix for it.  Such a simple problem, should have a simple solution.  We have to rework our board because of this.  If you cannot successfully do subtasks with Epics from the parent, remove the subtasks functionality or allow the ability to update the EPIC on the subtask.   

Please prioritize. It is a simple bug, but distrorts the main function of a board.

Happy 4th Birthday !

Even after having the all (parents) being assigned to the epic link, they are being shown as "no epic linked".

This issue needs to be fixed to provide better clarity for the team.

This issue needs priortization and needs to fixed urgently. This impacts our reporting

We are also on Jira Data Center and this affects our teams.

We are on Jira Server, but the issue is the same for us.

The whole point of subtasks in my view is to allow portions of a story to get assigned to other users. So avoiding assigning subtasks to different users is certainly not a valid work-around to avoid this issue. 

+1 for fix - Seems like a great function but useless with the bug as I get to many subtasks under the "issues without epic". 

This bug has existed since 2016 (or earlier). Tell us you don't care without telling us you don't care. The fact that you don't get a lot of public feedback on this isn't about the issue not being severe, it's about the lack of faith in your users to expect that if they report an issue it will be taken seriously.

No way is Severity 3 the correct classification. A feature broken in such a way as to be unusable does not have minor severity. The entire epic swimlane feature is critically broken based on this bug as we are not able to visualize and track work against epics with this bug in place. The definition of the feature is sorting by epic and the feature is not sorting by epic. For teams that rely on subtasks (another critical feature in Jira that probably every team uses), this feature appears to be faurly useless.

This affects my team standup every single day since we started trying to sort by Epic. Now I have to go talk to the Jira expert at my company* to either find a workaround or completely change how we go through tickets for daily standup.

• because doing simple things in Jira requires an expert to facilitate and companies tend to tie down Jira accordingly.

[venting over, please do better]

+1 for fix

I am facing the same issue with my team. What I don't understand is why the assignee of a sub-task has anything to do with the Epic link of it's parrent. The Sub-task should be set in the SwimLane of it's parrent no matter what it's Assignee is.

+1 for fix