Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Adding hierarchy tasks to an Epic is duplicated on Structure

I'm using Jira Structure, having this hierarchy: Epics -> Story -> Tasks.  

My goal - is to display & manage "Epic links" - with ALL the tasks that are located underneath a specific Epic on my Structure.

However - when I add tasks to a second-level under an Epic - it removes the Epic relations and set another link instead.

And if I'll add the "Epic relation" to a Task manually - it'll be displayed twice on my structure. - Once under the relevant Story and once under the Epic.

My goal hierarchy.

   Story (linked to an epic; relations to Task)
      Task (linked to an epic; relations to Story)


Please help

1 answer

1 vote
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 26, 2023

Hi @Yaniv Goldstein,

Happy to see you've made progress since you started this. Since you are trying to create a structure that is not natively supported in Jira, you'll have to be very rigid regarding the way you set up relations between issues.

Your observations are correct: if you add a task to an Epic, it will automatically appear in your structure as child of that epic, since the extender "issues belonging to epics" does render them. If you do not want them there, you should not add them to your epic, but only link them to the stories they belong to.

That may of course have an impact on the way you work in e.g. your scrum or kanban boards, as you will no longer see the link between tasks and the epics they belong to. So it's a matter of thinking thoroughly about what you are trying to achieve.

On a side note: the natural, built-in default child of a story would be a sub-task. You may be able to overcome the hierarchy issue you are trying to overcome here by using those instead?

Hope this helps!

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events