Does editing an issue during a issue created automation have a specific sequence?

rhylton

I'm trying to automate a specific field in our Jira workflow process.

I was able to get this working by using a Manual Trigger.

What i want is for this to happen each time a new ticket is created because the reporter missed the input, or it wasn't shown and i don't want to add a *required field.

Here is what parts of the automation look like as i started to strip down components to make it as simple as possible.

 

What i'm trying to do is this:

After the user fills out the issue, grab the value stored in Customer Site and store it in textCustomerSite

- I do this because I cannot do a comparison with a dropdown list.

From there, I then want to compare against that textCustomerSite to make another decision on what value goes into my last input "Owner Type".

It seems that though i was able to get the value into textCustomerSite, the rest of the Automation doesn't know that the value is there, as though it hasn't happened as yet.

 

Please advise/Point me to a resource

Thank you!

Bill Sheboy

Hi @rhylton 

By default, the state of the trigger issue(s) when it loads is used for the rule actions, conditions, branches.

When your rule edits the issue and you want that value to be used by later steps, add the Re-fetch Issue action after the edit.  This will slow the rule a bit and reload the data before proceeding.

The exception is if your edit happens within a branch that could be on more than one thing / issue.  Those execute in parallel and asynchronously, and so the changes are likely not visible outside of the branch.

 

One more thing...your rule is using the Issue Created trigger.  That one can fire so quickly that some data may not yet be available to the rule, leading to unexpected behavior / errors.  The fix for that is to always add the Re-fetch Issue action immediately after the Issue Created trigger.

 

Kind regards,
Bill