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

Allow issues hierarchies with Parent Link and Epic Link

In our Jira instance, we have renamed our epics to features and created a new type of epic ticket.


This configuration brings a new hierarchy between our tickets.

Epics > Features > Other ticket types (US, Tasks, Anomaly etc...). We represent this hierarchy by the "Parent Link" (Parent Epics and child features) as well as the "Epic Link" (with the other types of tickets below the Features)


The current configuration of the dependencies does not take into account the native Parent Link and Epic Link Which prevents a hierarchical display of tickets in the dependencies.


We opened a ticket at Atlassian support, and then a ticket was created on their side. We need a vote to allow the implementation of these links in the dependencies. FYI :


I'm forwarding you the ticket, feel free to vote and follow if you are interested in this feature.Advanced Roadmap.PNGDependcies Link 1.PNGDependcies Link 2.PNG



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events