JPD Automation to populate Idea Custom Field with EPIC issue.url

[Corey Hampton]

In JPD I created a global custom field called DEV Epic, type = URL. I created the following automation rule according to what I can find online but it's not populating the DEV Epic correctly. 

Instead the Idea issue.url is being populated in the DEV Epic field. 

When a Delivery ticket is created from JPD or linked to an existing EPIC I want the EPIC issue.url to be populated in my custom field called DEV Epic. 

My goal is to make it easier to get to the Epic instead of having to open the Idea, go to Delivery then click on the link. Any help is appreciated!

[Bill Sheboy · Accepted solution]

Hi @Corey Hampton 

For a question like this, please also post an image of the audit log details showing the rule execution (with all of the areas at the right side expanded).  This will provide context to better understand how the rule steps processed.

Until we see that...

Where is your rule defined (i.e., in a project or in global automation) and what is the rule scope: single-project, multiple-project, or global?

Your rule is likely trying to branch to an issue outside of its scope, and so cannot see it.

Kind regards,
Bill

[Corey Hampton]

Sure thing. Here you go.

Automation is for multiple Jira Projects and 1 Product Discovery

[Bill Sheboy]

To confirm, are you trying to copy the URL to issue PD-122 into the PMO-180 Idea's "DEV Epic" field?

If so, branching to the destination issue will try to update the incorrect one.  Instead try updating the trigger issue (without the branch) using:

{{destinationissue.url}}

Or, using Lookup Issues with JQL to ensure you get exactly the one you want. 

[Corey Hampton]

I'm trying to copy the (Dev Project) PMO-180 issue URL into (Idea) PD-122 custom field. Right now, it's populating the PD-122 issue URL in the custom field.

I can try this. I was looking for it in the smart fields and it didn't come up.

{{destinationissue.url}}

[Corey Hampton]

I just changed issue.url to destinationissue.url and the same behavior is happening. 

The URL for PD-122 was added to the custom field, when it should be the URL for PMO-180

[Bill Sheboy]

Thanks for clarifying: the rule is branching to the Idea (i.e., the destination issue), and so the value that should work is {{triggerIssue.url}}

[Corey Hampton]

That was it! Thank you Bill.

[Bill Sheboy]

Awesome; I am glad to learn it is working!  Please consider marking this question as "answered" to help others with a similar need find solutions faster.  Thanks!