The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
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.
1 comment
Comments for this post are closed
Community moderators have prevented the ability to post new comments.
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.
