You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I create an Automation in which I fill the Description if it's empty before create an issue on which I use this field value but it seems that the rule process the creation before ending the update of the field in the original request.
the log :
Is it possible to wait the effective update of the field or to execute a "commit" ?
Hi @Gregory BENARD,
If I'm understanding correctly, you will want to set the trigger to kick off when an issue is created. Then you'll check if the description is empty and if so, make your edit.
With automation you cannot take any action until the ticket is created.
Thanks Matthew. @Mathew Lederman
In fact, I run a manual rule on an issue to create another issue on another project.
For create, I need the description because this field is mandatory in the destination project.
So I check on the original issue that the description field is not empty and if not I put a default value "To be completed" before using Create Issue component in my rule.
But it seems that the Create Issue component is processed durng the modification of Description is already in progress.
In that case I think you need to use the If function alongside the Create option:
Automation rule logic uses the information in the trigger issue(s) from the time of the rule start.
When you update a trigger issue in the rule and want to use that update later, please add a Re-fetch Issue action after the edit. This will reload the data before proceeding.