Clarification on Transition

[C M]

I just want to some clarification regarding transition and automation using issues transitioned.

1) If you're updating a custom field in the post function of a newly created issue does the change commit before FIRE ISSUE CREATED event? 

2) When a newly created issue transition to the next status after creation does the automation read that as an issue transitioned? Or only manually transitioned issue only trigger automation rule that use this trigger.

Scenario: I have a post function that updates custom field and I want the automation to read the custom field. It doesnt seem to work. I tried to use trigger transition and using the first workflow status after creation as a trigger but it doesn't seem to recognize the transition.

[Marc - Devoteam]

Hi @C M 

1. No, after. It can't do it before, as there is no issue
2. No, this is the initial status of you workflow that is set on Issue Creation

What you could do in the automation set the trigger on Issue Created and the next step is to use the action Re-Fetch Issue Data.

This will get the data of the created issue, then you should be able to read the input of the custom field.

[C M]

HI @Marc - Devoteam, it still doesn't seem to work. I have updated automation based on your recommendation and it still does not read the custom field, it should set the status to OPEN but instead it triggers the status of the else condition.

[Marc - Devoteam]

Hi @C M 

The copy values needs to be at least after the actions 3 and 4.

To get to the solution and mitigate, make a copy of your automation and change edit action on the if and else condition.

If need to match add a comment, say success and other not successful.

But it can simply be a timing issue, that the copy action you do n the post function is taking to long before the automation already actions

[C M]

Hi @Marc - Devoteam 

I tried what you suggested it seems like its a timing issue, so might just do a scheduled automation.