Hello,
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.
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
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.)
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 https://support.almworks.com
Hope this helps!Igor
hi @Igor Sereda [ALM Works] Like parent Field , can we create a custom field which does the same requirement like Parent Field? in which we can get Issues from which we can set an issue as parent issue, like we do in Parent Link Field.
Hi J!
Thanks for your post.
Can you clarify whether you're looking to use Structure to create a custom field similar to Portfolio's Parent Link field or you need a way to create a field in Jira that's similar to the Parent Link field without using Portfolio?
Perhaps you can elaborate more on your use case so I can better assist you.
Best Regards,
Vlad
ALM Works
Hi @Vlad[ALM Works]
Thanks For you reply, i need 2 Help :
1 : - you need a way to create a field in Jira that's similar to the Parent Link field without using Portfolio - How this is possible?
2 : - i need to Link one Issue to Another Issue but not as Parent Child Relation, how to do that ? i mean i dont want to use Parent Link Field .. i found one option Called Issue LInked(Blocked, Relates To etc type), can we create using Linked Issue? And if we can create using Linked Issue , Then rather than Naming Linked Issue can i gave my Own User Defined Custom name ?Here you can i have created a Issue Linked , Designed For, what i need is that Designed For Should Come as a link when i am creating a Issue, Currently its coming as Linked Issue field , inside that i have Defined "Designed For".
That i need help.
Manas
It looks like you're new here. Sign in or register to get started.
![Photo of Igor Sereda [ALM Works]](https://us.v-cdn.net/6038660/uploads/avatars/91/c0/n91c0d44c3025693ab41c518ac13e240c.png)
![Photo of Vlad[ALM Works]](https://us.v-cdn.net/6038660/uploads/avatars/07/67/n0767005f92a3444ea55c18f33200b171.png)
