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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Hello,

 

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.

Automation - Jira - Google Chrome_3.jpgthe log :  Automation - Jira - Google Chrome_4.jpg

Is it possible to wait the effective update of the field or to execute a "commit" ?

Thanks

2 answers

2 accepted

4 votes
Answer accepted
Mathew Lederman
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.
Nov 03, 2023

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.

Like Sanjog Sigdel likes this
Mathew Lederman
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.
Nov 03, 2023

In that case I think you need to use the If function alongside the Create option:

  • If description is empty, Create with your default description as part of the new ticket fields
  • If description is not empty, Create with the description provided in the original.

Thanks @Mathew Lederman In fact, Bill give the right answer by using Re-fetch data component.

1 vote
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.
Nov 03, 2023 • edited

Hi @Gregory BENARD 

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.

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Re-fetch-issue-data

Kind regards,
Bill

Like # people like this

Suggest an answer

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

Atlassian Community Events