Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Retrieve informations of linked Issue in automation

Steeve P_
Contributor
December 18, 2025

Hi everyone , 

As admin, i'm in charge of finding to make everything work smoothly , on each of ours space.

One existing automation , is to create a linked Issue (A) , and on the created one (B) add a comment (Comment is the "A"last one) + Showing Actual SLA inside the comment in "B"

Would basically look like

Issue A --> Transition trigger automation --> Create Issue B --> Copy last comment of A to B + SLA

We had huge problem with the SLA part as most of the time SLA is still not calculated by the time the automation finish.

Did few search and make it more reliable by triggering a second automation when the first one have created the second Issue
Second Automation will be in charge to check if value exist , of not to loop on itself wait 10 sec , fetch and then add comment.

For the SLA Part...Seems for reliable than having it inside first automation.
But for the comment part... I can't retrieve thoses information from the linked issue.

I thought of putting the loop inside the first automation, but as the creation of the issue "B" is already behind an IF/Else , and branching, I can't recreate one on that level :/

So ...I'm looking for idea and Advice. ;-)

Capture d'écran 2025-12-18 120537.pngCapture d'écran 2025-12-18 120552.png

 

2 answers

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 18, 2025

Hi @Steeve P_ 

Based upon the rule images you show, and without seeing the specifics of the Edit Work Item actions and audit log, I wonder...

  • When the new / linked work item is created, why not set all those fields at the same time during the create action?
  • When adding the comment (after branching to the most recently created work item, you could get the last comment from the trigger one with {{triggerIssue.comments.last.body}}

 

Kind regards,
Bill

Steeve P_
Contributor
January 4, 2026

Hi Bill , 

First of all , Happy New years ;-)

Sorry for delay but was on holiday and had a little personnal problem to start this year...

 

For most of the information, I can retrieve them correctly.

My main problem is located arround the SLA , and trying to get everything working around them.

 

I can try as hard as I want , I'm unable to be 100% sure that SLA will be calculated before I try to get them inside a comment.

 

That's also why I gave a try with a second automation (can't create a loop on the first one) to get some king of "loop" but even like that, I would say...it only succeed 75% of the time, 
25% , SLA is just Empty / Not calculated yet.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 5, 2026

Hi @Steeve P_ and Happy New Year!

I wonder if the problem is the racetrack timing when the SLA value is available.  There are a couple of things to try before using it in the comment:

  • As you are on a Premium license level, you may add a Delay() action followed by a Re-fetch Work Item Data action after the trigger.  This will add a pause and reload the data before the rule steps proceed.
  • Another possible cause of timing problems is some smart values are read just-in-time...and thus may not be read fast enough for the action that uses them.  The mitigation for that is to store the smart value (e.g., the SLA) with the Created Variable action and then use the variable in the later action.  This will force full evaluation of the smart value before the next rule step.

 

Please let me know how those impact the rule behavior.  Thanks!

 

Steeve P_
Contributor
January 5, 2026

Hi Bill

 

I did try this way as well

Here is Screenshot of the actual rule in production that's is currently working (but not so well ;-))

That's what made the team ask me to find solutions cause , there is too much time that the SLA doesn't show inside the comment.

image.pngCapture d'écran 2026-01-06 075437.pngCapture d'écran 2026-01-06 075556.pngCapture d'écran 2026-01-06 075529.png

 

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 6, 2026

I believe Delay() on the main rule path has mostly predictable behavior, but I do not know about inside of a branch.  Please try moving just the Delay() action to immediately after the trigger to see what happens.

 

If that does not help, I recommend asking your Jira Product Admin to submit a ticket to Atlassian Support here:

https://support.atlassian.com/contact/#/

You appear to be on a paid license level, and so the admin can submit the ticket.  When you hear back from the support team, please post what you learn.  Thanks!

0 votes
Steeve P_
Contributor
December 18, 2025

Edit : don't know what I did but posted the screenshot as an answer...Sorry

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events