nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Retrieving created issue Key to update the Trigger Issue

Jose Ramon Sagarna

Hi,

I'm trying to retrieve the key from a created issue to fill a custom field in the trigger issue.

Trigger and Created issues are in different projects and are sub task types

Problem is that I need to branch it to retrieve data from the Created parent issue to gather the key of a previously created issue that will be the parent of the new one in a different project)

Trying so many ways API seems the direction but I get a 405 whenever i try to use smart values in the URL.

Any clues?

Thanks in advance

Accepted answers

All comments

Bill Sheboy

Hi @Jose Ramon Sagarna

If you write that constructed URL to the audit log, what do you see?

And, have you confirmed your request is set up correctly. Please see this article for an example: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Kind regards,
Bill

Jose Ramon Sagarna

Hey Bill, thanks for answering

Got a 405 error:

Error publishing web request. Response HTTP status:
405
Error response HTTP body:

If I change {{issue.parent.key.urlEncode}} to for example ABC-1 it works

And yes, i saw that one and i followed it

Bill Sheboy

Understood, but if you write that dynamic URL expression to the audit log, run your rule, and post the audit log details, it may reveal this is not formatting as expected.

My guess is this is caused by one of two possibilities:

There is a known issue with the Issue Created trigger that it can fire so quickly that the issue data is not present at the time the rule runs. The impact is missing data could cause actions / conditions / branches to not behave as expected. The work-around for that is to always add a Re-fetch Issue action immediately after that trigger type, which will slow down the rule by about a second and reload the data before proceeding.
For some other reason, your fields / smart values are null, leading to an invalid URL for the call

Jose Ramon Sagarna

i see, couple of questions to confirm,

I should be able to get the data from the trigger issue even if i am in a branch, right?
If that's so, i've see two ways {{issue.parent.key}} and {{TriggerIssue.key}}, do you know if there any others?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

automation