Heads up! On March 5, starting at 4:30 PM Central Time, our community will be undergoing scheduled maintenance for a few hours. During this time, you will find the site temporarily inaccessible. Thanks for your patience. Read more.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Can't get fix version value of trigger issue

sacha_rouzkhosh February 5, 2024

Hi everyone,

I have created an automation with the following actions:

  • Upon the creation of an Epic with a specific component, Jira sets the fix version;
  • Subsequently, child tickets are created, and Jira sets the labels using a concatenation system: "fixVersion of the Epic" + "_" + a certain variable.

It seemed to work well, but I don't know why I can't get the fixVersion value anymore.

Here are some details about the configuration:

Screenshot 2024-02-05 at 10.32.11.png

 

Screenshot 2024-02-05 at 10.37.46.png

I also tried:

Screenshot 2024-02-05 at 10.38.55.png

 

Here is the log detail:

Screenshot 2024-02-05 at 10.33.44.png

Thank you very much for your assistance.

2 answers

1 accepted

0 votes
Answer accepted
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 Leaders.
February 5, 2024

Hi @sacha_rouzkhosh 

There are two challenges with your rule:

Your rule edits the issue and then tries to reference the field which was just edited.  The rule cannot "see" those changes for later rule steps, as it still contains the values at the time the rule started.  To use the changes later in the rule, a Re-fetch Issue action must be added after the edits.

 

Another possible cause of this symptom is the Issue Created trigger can fire so quickly that some of the issue data is not yet available to the rule.

The fix / work-around for this is to always add the Re-fetch Issue action immediately after the trigger.  That will slow the rule down a bit, reloading the issue data before proceeding.  Please try adding that action and re-test.

Kind regards,
Bill

sacha_rouzkhosh February 9, 2024

Thanks a lot @Bill Sheboy 

The re-fetch fixed the issue.

Like Bill Sheboy likes this
0 votes
Kalyan Sattaluri
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 Leaders.
February 5, 2024

I dont see you using your variables in branch, also can you confirm if your epic has a version when created?

So my first suggestion is to log  {{issue.fixVersion.name}} before your branch to confirm that works, 

second, put an if condition to check if you have a fix version, then you update child issues if it exists.

Also for your variables, please update with fixVersion instead of fixVersions

 

 

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events