Good morning,
In the automation we are using the Advanced branching branch, to create tickets depending on the asset(s) selected on a ticket. So, for each asset, a ticket is created.
However, for those newly created ticket I would like to edit them. Howvwer, the branch "All creating issue" or "Most recently created issue" doesn't work, I have this error:
Hello @Bastien Delourmel
I suspect that your problem is due to Branches being executed in parallel, not sequentially.
Your branch to iterate over the created issues to edit them is running at the same time as the branch that is creating the issues.
You need to incorporate the step to edit the newly created issue in the same branch where the issue is created.
Hi thanks for your return.
However, it is not possible as after the action "Create a new issue" my only possibilities as new components are "Add an action" or "Add a condition".
It would be possible if I had the ability to add another branch to this current branch to say "Most recent issue created" or "All creating issue"
In the mean time I have another rule running saying "If ticket are linked" then edit those ticket. Even though is it not the best, because it consumes numbers of executions, and I would prefer edit the ticket in the same automation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that is true. My suggested fix is incorrect. Just adding an Edit action directly in that branch would Edit the issue selected by the branch, not the newly created issue.
What field are you trying to Edit in the newly created issue?
Many issue fields can be set directly during the Create Issue process. Perhaps you can complete the field edit within that step instead of having a separate step for it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am trying to edit the request type
I first thought of "Creating Request Type issue" action instead of "Creating issue", however in the request type the field needed are not in the request type form so not available in the automation rule
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.