We've created an offboarding form.
In this form, by checking a box, you can choose the applications from which the account should be deleted.
I'd like a new ticket to be created according to a certain request type depending on whether the box is checked or not and I'd like to configure some fields like the team assignee, application (custom field) and change of description and the summary depending of this application. For each application, the information is different.
If I do my automation as below, the new ticket is created but the changes are made to the ticket that triggers the automation.
so I thought, I'll make branches, one for each application
but that doesn't work either. it creates the ticket but applies the changes to the same ticket...
please help me
Hi Valérie - Welcome to the Atlassian Community!
Add a Branch under the the action where you are creating the work item and select Most Recently Created Work Item. Then move your Edit Work Item function under the branch.
Thanks!
You mean I add a new branch and keep the first or delete the first and add another?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't know what you are doing with those other two, but to update the issue you just created you add the new branch and move the action under it.
What are you trying to do with the other two branches?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I try to create another issue for each application.
I'll try your option and update here. Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ok I made the changes and it doesn't work well.
the first "IF / Branch" work well but not the following "IF". The rule stop it execution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, I am not following as to what worked and what didn't work. Can you provide a step-by-step use case and note at each step if that worked or didn't?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Valérie GOMBERT,
Welcome to Atlassian Community!
The reason the changes are happing on the triggering work item is because the focus is on that, even when you use the "For current work item" branch. Instead you have to use the "For: Most recently created work item", that way the focus will be shifted to the work item you created in the automation and not the triggering work item.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.