nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation

Gregory BENARD

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.jpg the log :

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

Thanks

Accepted answers

Mathew Lederman

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.

Bill Sheboy

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

All comments

Mathew Lederman

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.

Gregory BENARD

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.

Mathew Lederman

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.

Bill Sheboy

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

Gregory BENARD

👍 Thanks @Bill Sheboy

Gregory BENARD

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud