I've created an automated rule to automatically create a ticket to a separate JIRA board once a field value has changed. However when that ticket is created, it's not automatically linked in the JPD idea as a delivery. Can this be done?
For example:
Field value changed -> Work Required -> Automatically create a ticket to separate JIRA KANBAN Board. This can be done.
But im discovering that the ticket created in the KANBAN board is not automatically linked to the original idea in JPD. Can i do this? I would like it to be automatically linked and therefore the progress status be automatically updated in JPD board.
Community moderators have prevented the ability to post new answers.
In your automation rule, when creating the ticket within the Jira ticket, you can link it to the Idea ticket within the JPD project using the "Polaris issue link" link type. From the Jira ticket, the linking would be "is implemented by".
Hey @Gary Spross thanks for the response. Did you mean creating the automation rule on JPD itself or in the Kanban board? I have tried and wasn't able to find a "Polaris issue link" I have managed to just automatically link the issue however it's not linked as a delivery ticket.
Screenshot 1 (initiative 4) is automatically linked to the JPD idea as a linked issue but not delivery issue and screenshot 2 (initiative 1) is when i manually add the link of the ticket created in the Kanban board. I was wondering if we can automatically link it so that it shows as a delivery ticket?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your linked issue, URPR-9 is linked using the "relates to" link. It would need to be linked using the "is implemented by" link.
In the automation rule you have that is creating the "delivery" ticket within the Jira project, you can add the "Link issues" component like this:
NOTE: I'm assuming the trigger for the automation is a field being updated within the JPD Idea ticket, so using the "Trigger issue" in this component should work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've tried this but it hasn't worked. It hasn't linked the issue at all when I used "is implemented by" instead of related to. Any thoughts?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmmm...
For me, it shows within an Ideas panel on the Jira ticket, like this:
and within the Delivery panel on the JPD Idea ticket, like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried again today and this works now ! Thank you. Probably a glitch yesterday. Tried the exact same thing but it's linked as delivery tickets now. Thanks again for your help :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried the suggested steps, but they are not working in my case. The automation currently in place to automatically create tickets in the delivery project and link them as “is implemented by” is creating a standard Jira issue link, similar to what is used across regular Jira projects.
Because of this, the linked tickets are not appearing in the Delivery relationship. It seems that when tickets are created or linked through automation, they are treated as normal issue links rather than the special linkage used by Jira Product Discovery.
However, when a ticket is created or linked directly from the Delivery tab of an Idea or Bug, the relationship is established correctly and the ticket appears under the Ideas/Bug section in the delivery project.
The same behavior occurs in the reverse scenario as well—linking the delivery ticket to the Idea/Bug from the delivery project side using standard issue linking also results in a normal Jira link and does not populate the Delivery relationship. Only when the linkage is created through the Delivery tab does it reflect correctly on both sides.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@PoojaC, this topic has been locked because the thread has become a bit dated. If you’d like to keep the conversation going or have additional questions, we encourage you to start a new topic. You can read more about necro posting (“raising threads from the dead”) in our Community Guidelines.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.