597beb9eaea9 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!

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 !

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

+1 for fix - really annoying bug

+1 for fix

+1 for fix

+1 for fix

Was created in 2018. Please fix this already.

+1 for fix

+1 for this one. Pls fix

Please fix

+1 We miss sub tasks because they unexpectedly show up in the 'issues without epic' swimlane.

+1 on this task

I concur with the above comments, would be good the get this fixed as a higher priority.

+1 on this.

@Atlassian - Your policy on bugs says, for Medium:

• The application or specific feature isn't working as expected, but there is a workaround available. Users' experience is impacted, but their job function is not impaired.

Yet, there is no workaround for this. Doesn't that mean this would be categorized as a High?

Fix this please, this impacts core Jira functionalities, how can this be prioritized as a Low?

+1 please fix asap

@Atlassian,, this issue has been in gathering impact since  jannuary 2020 and it is obviously a bug (not a feature request) so maybe it is time to start acting on it and try to resolve it???
This is very confusing for users !

+1 on this!

+1, please fix asap.

Ooof, this is really annoying as we rely on subtasks heavily. +1 to fix this.

+1 for this one, we are missing the flexibility and visibility for sub-tasks.

Plus 1 on this being a high priority issue.

We split a task into sub-tasks and assign the sub-task to different team members. The project tracking is misleading, because it does not show the sub-tasks under the correct epic and it makes it easy to miss important work.

Is this a duplicate of JSWSERVER-11823 and JSWSERVER-10683 and JSWCLOUD-16752 and possibly others? I'm pretty sure if you add up all the voters from all these issues it would be a bit higher in priority?

We have the same problem, using Epics for lanes should ideally include the subtasks as well - the links are there and we expect them to be used.

This is impacting my team as well. Some sub-tasks just hang out at the bottom of our board rather than in its Epic's swimlane.

Experiencing this as well. It's illogical that a sub-task would appear outside of an epic swimlane if all the linkages are in place (i.e. epic - story - sub-task) — don't see how this priority is low, the tool is broken? Or do let me know why a sub-task being done by someone different to the story assignment should cause it to be orphaned on a board with epic swimlanes

same here. real pain in the a**s. very misleading.

Same issue here. I would expect that subtasks are always shown in the swimlane of the parent Epic. Without any special settings. The subtask is already linked to the parent epic so what seems to be the problem why this is working as expected?

Hi,

We also faced this issue.

We created a board and based swimlanes on Epics.
If a task is assigned to colleague A, sub-task to colleague B and colleague B click on the filter, then the sub-task of colleague B is shown on Dashboard under Issues without Epic (the Epic is the project/scope they are working on).

This board is part of the team member's day-to-day work and it is very important that it will display the correct data

Find this incredibly frustrating. I'm trying to encourage a good issue hierarchy with my team but this bug undermines what I'm telling them.

I had this problem too, and worked with Celso with Atlassian support to create a workaround. Below is what we did, and seems to work:

1. Created a custom text field. Needs to be a text field to work with next steps.
2. Used Jira automation to run on issues created within an Epic for Issue Types Stories, Tasks & Bugs to populate the custom field with the actual Epic Name
3. Same for Sub-tasks, when created within a Story, Bug or Task, Jira automation will populate the custom field with the parent custom field name (which was taken from the Epic name)
4. Changed board swimlanes to sort by queries instead of epic
5. Wrote a query for each epic we had, and will have to going forward. Named the query based on the epic name, JQL search is "<custom field name> ~ nameofepic populated in the custom field"

End result is the board looks and feels like it would based on epics, but is based on queries.. and when you filter by an assignee, the sub-tasks still show up under the epic.

Note: Team members will need to make sure they always create tickets within an epic, but if they don't I set up another filter on the board to search for issues that have the custom field empty... I called it "Issues without Epics" 

This affects my team as well and makes it difficult to properly view and track progress

This impacts our teams as well.  We use subtasks extensively and use the tool across our company.  It just doesn't make sense to handle sub-tasks like this.  I agree that from an end user perspective this is higher priority than a lot off the UI tweaks that have been implemented over the last couple of years.

This long standing bug damages the credibility of the swimlane view. As soon as sub-tasks are assigned to people they get dumped into issues without epics making it harder to progress Epics across the board.

I do not think this should be considered low priority.

Priority low... Please fix this quick, this core to the way Jira is supposed to dispatch and render its data through the boards.
Stop fiddling with the UI a little bit and focus on the right stuff at Atlassian.

This affects my team as well. We have a lot of similarly-named Stories/Sub-Tasks (i.e. "Development", "UAT"), which are usually easily distinguished by the Epic Labels and by configuring the Kanban Board to have Epics as swimlanes. Having "stranded" Tasks under "Issues without epics" causes meetings to get derailed by looking up the Issue Details. It seems to get worse when filtering by users.

This affects and effects my team as subtasks do not display under the Epic view on the Kanban Board. 

This is effecting my team as well. Sad to see it is Low Priority, but understandable. I'm, commenting to contribute to the "Gathering Impact" part of the workflow.

It causes confusion in my team, both for people creating the sub-tasks, and people receiving sub-tasks. The "Issues without Epics" column gets pretty stacked and uncategorised. This happens when we want to push certain sub-tasks from stories to get them started sooner, while the rest sit in Backlog.

I might have found the issue.

If you use Epics as swimlanes on a kanban board and all issuestypes, like; Story, Task, etc.., are linked to a parent (Epic).

All seems fine even using quick filters and/or a specific user (myself).

The problem starts when sub-tasks are assigned to other people than the assignee of the parent task.

Then you get the strange result that those sub-tasks end up showing under "Issues without Epics"

This also impacts our team. Would like some focus on this.

Seems there is more backing on the Server Product, but it effects everyone.

This should be high priority.
The most my kanban board users are not capable of managing this and this issue cause a lot of confusion for them.