You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In my Epic type I have the option to "Create Child issue" which lets me set that to a User Story, task, etc but in my Initiative type, it has "create sub-tasks".
How do I switch my Initiative to have the "Create Child issues"?
Hi @Sean Grant ,
Epic level can't be changed.
In this hierarchy level you may just add levels above epic and add them as a parent to the epic using parent link field.
And actually, the "Add a child issue" button won't appear, but you will be able to link issues above epic with Parent Link field, i.e.
The Stories, bugs, Task etc. have epic link and you put their parent there.
The epics should have parent link and you can put their Parent initiative there.
Hope it makes sense!
@Magdalena Zhisheva Are there any plans to address the fact that a large portion of the community absolutely hates this functionality, and the fact that Atlassian is actually hampering our ability to operate correctly, just not according to their standards of correctness?
The entire hierarchy system that is in place is forcing us to work inefficiently, and as I have read copiously from your actual users in the community that many feel this way, and have just accepted that no one at that company listens or cares.
If I had the final say, I would cut Atlassian completely from our company at this point and find better alternatives, I've been using Atlassian for years, but have found recently it to be very impeding in the areas I need it not to be the most, especially as I am the QA Manager and cannot make your tracking system work the way our Dev team/my QA team need it to, and it is literally because Atlassian has "decided" that this is not the "right way" to do things.