Issue Links and Parent Link



We are using both Issue links (realizes/realized by) and also Parent Link field to enable JiRA Portfolio. At times we are seeing mismatch between issue links and parent link as user sometime not linking the right parent in both the links.  We need help with some jira schedulers that can sync the values from issue links to Parent Link so that both are pointing to the same parent issue. Please share your suggestions.

2 answers

0 votes

Hi Karthikeyan,

If I understand correctly , it seems like your process requires setting the parent issue and the linked issues field to the same issue, which sounds redundant.  I like the "liked issues" and I use it frequently but to refer to a parent issues I would rely on parent issue.  Can you share more details about your use case, and why you would need both?  Thanks!  Carlos 

Hello Carlos, Thanks for your response. Here is my use case.

We want to use both JiRA structure as well as JiRA portfolio


JiRA structure works based on Issue links, so that Structure has the drill down from Epic to Stories and subtasks

JiRA Portfolio works based on Parent link. We need portfolio view to view the release timeline view and also to view the hierarchy from Epic to Stories

This is our use case. We can achieve this only by ensuring that both issue link and Parent link is set to the same issue. 


I need a way way to automatically sync the parent link based on issue link or at least I need a dashboard to show the mismatches to make the corrections manually.

Hope this helps

Like 1 person likes this

Hi Karthikeyan,

You may need a plugin to do this. Script runner extends JQL functionality .  There is another plugin, SQL for JIRA, that may be helpful too (converts JQL into SQL.)

Hi Karthikeyan,

Which versions of Structure and Portfolio are you using?

The latest versions of Structure actually integrate with Portfolio and support the Parent Link! You don't need to replicate the Parent Link with Issue Links -- unless you're using older versions.

If you're familiar with Automation feature, Structure has an extender "Child Issues (Portfolio)" to build the hierarchy down from the top-level items and a grouper "Parent Issue (Portfolio)" to add a higher level on top of Epics. These generators are also able to interpret your drag-and-drop actions to change the Parent Link in Portfolio.

If you have any questions about using these features or need help, please open a support request at

Hope this helps!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 14, 2019 in Jira

Updates to give you visibility into what's coming in Jira Server and Data Center

Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...

758 views 1 17
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you