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

Next-gen - Epic vs Add to parent Issue

Why would you guys change "Epic" to to "Add to parent issue"? it is something that everyone has been used to and plus when you click on this it still shows epic on the page ... 


1 comment

Eoin Atlassian Team Jun 11, 2019

Hi Sam. Thanks for the feedback. There are two main reasons we have done this...

1. We are looking to be more generic as we add additional levels of work hierarchy. Currently we have 3 levels and we will look to increase this further in the future.

2. Each level of hierarchy may have more than one issue type. This is currently only possible at the base level.

The caveat here is we will look to introduce hierarchy level names (and likely the ability to edit these names) in the future. At this point we may revert this action to use the hierarchy level name rather than using the parent term.

Going forward, we will focus a bit more on our "change boarding" experience as we introduce further changes to next-gen. We want to avoid surprises like this where possible. Again thanks for the feedback.


Eoin (Product Manager)


Log in or Sign up to comment