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!


Portfolio_linking is not working properly. not in sync with Jira

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 answer

0 votes
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 04, 2020

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

Viasat Inc.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events