What is the best way to move a ticket via automation within the same project, when both the Issue and Request Type are different? If X conditions are met on the form, the ticket needs to move. The Issue Type always updates fine but then errors out on changing the Request Type. I can't seem to get it working, I assume it's primarily because I can't make the rule run in a specific order and have the Issue Type change first, then Request Type.
Hello! Have you tried adding a re-fetch action after the action that changes the issue type? If you configure the rule to edit the issue type, then re-fetch the work item data, then edit the request type, that should resolve the issue.
But I can't make the re-fetch rule run specifically after changing the Issue Type, right? Since I can't tell the rule what order to run in? If the re-fetch can happen at any point in here, it can happen before the Issue Type changes, which is pointless.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It runs in top-down order. So the way you have it configured in this screenshot should work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @NoName
Can you provide a screen image that shows your entire rule?
If the rule you have shown in your response to @Lacy Saute is generating an error, what error are you getting? Please provide screen images that show all the details in the rule Audit Log for the rule execution. Make sure to fully expand each entry within the rule execution log entry so we can see all the details.
It is generally not advisable to change issue types using the Edit action unless the issue types are configured to use the same workflow, field configuration, etc. Otherwise there may be requirements of the destination issue type that are not getting met.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@NoName -
I agreed with Lacy's response. Can you provide a bit more information of the following -
Issue type A associated with Request Type X
Issue type B associated with Request Type Z
So, if the FORM conditions met - you want the rule to switch Issue Type A (Request Type X) into Issue Type B (Request Type Z)?
I look forward to your response.
Best, Joseph Chung Yin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have a hunch the issue comes from changing both the Issue Type and Request Type at once – try updating the Issue Type first, then use a Re-fetch action, and only after that change the Request Type, or split it into two separate rules.
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.