Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

All Tasks with an Epics are not showing in their own sprints But showing in Backlog



We do not change any settings for Jira. Instantly we noticed that Tasks are not showing in the Backlog. All of the Tasks have been moved from sprints to the Backlog expect some. I debug this issue and noticed that Those tasks which have been assigned to an Epic are showing in the Backlog Section. I have also checked the sprint associated with these tasks and the sprint value in the tasks is correct.

We have some inactive sprints in the Backlog. The tasks should need to show in their own inactive sprints but rather than that all tasks are sowing down in Backlog section.

See  image Below

Jira Issue.png


Now if i will remove Epic from any task then it is showing the task in its own Sprint. I tried to solve this issue but do not get it sorted....


Any help would be appreciated.


I'm having the same exact problem! Any clues of what could happened to us?

Sam Hall Rising Star May 09, 2017

If you are on JIRA Cloud and are sure you haven't changed anything, I'd suggest raising a support ticket with Atlassian ( and linking to this thread.

I'll do that! Thank you Sam, please let me know if you get some more information about this!

Sam Hall Rising Star May 09, 2017

@Gonzalo - I'm just a user like you, so there's not much more I can do. I've just noticed the trend in questions around the same issue.

Please let us know on here what the outcome of your support request is - it'll help others experiencing the same issue.

Sam Hall Rising Star May 09, 2017

Just to close this off.

Atlassian confirmed it was a bug affecting Cloud, which is now resolved.

More info:


Lads thanks for your response. It was a cloud issue that Atlassian guys already fixed.

Follow links mentioned above by Sam Hall

Lads thanks for your response. It was a cloud issue that Atlassian guys already fixed.


Log in or Sign up to comment