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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When we create an issue-epic from protfolio as a child under capability, after reviewing the changes, save in Jira. it is not accepting. The epics are left orphan.
After many months no resolution received yet.
Hi Mr. Macias:
Did you establish the hierarchy properly via the add-on's Hierarchy Configuration? I assumed that "Capability" is the direct parent of EPIC.
Your configuration should be
Capability (issue type)
---> Epic (issue type)
If it is not, then your action will not work. You can also expose the field "Parent" in your plan to verify that your new EPIC's parent is indeed associated with the Capability issue as a child. See example below, we have an issue type of Initiative setup in the hirerachy as a direct parent of Epic.
Hope this helps.
Best, Joseph Chung Yin
Jira Functional Lead - IT Global Infra Apps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.