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.
×Hi everyone,
I have created an automation with the following actions:
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:
I also tried:
Here is the log detail:
Thank you very much for your assistance.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.