Automation rule for the Same workflow using three different request types.
Asked by Prinka Rai:

When a new ticket has raised using one of the three request types using the same workflow and issue type, the ticket remain unassigned.

I want it to be auto assigned to a set user.

automation rule i have set as:

![Capture.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/315889iC3BD542177033E24/image-size/large?v=v2&px=999 "Capture.PNG")


Answers:
author: Mauricio Heberle
body: Show us your automation log


author: Darryl Lee
body: Hi [@Prinka Rai](/t5/user/viewprofilepage/user-id/4107877) - you're on the right track. You'll need to make sure when you create a Condition that you allow for additional clauses (different **Issue Types**) via the ELSE IF function buy hitting the button I've circled in red below:

![Screenshot 2024-04-02 at 4.06.51 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/315890i675836F4FA89768A/image-size/large?v=v2&px=999 "Screenshot 2024-04-02 at 4.06.51 PM.png")

You would then simply add your conditions for each clause. So I don't have a **Support** issue type, but selected **Bug** , and then **Story:**

![Screenshot 2024-04-02 at 4.10.18 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/315891iEEE6F8876144E2DF/image-size/large?v=v2&px=999 "Screenshot 2024-04-02 at 4.10.18 PM.png")

You can add that at the end of your existing rule, and then drag your Blue action blocks into the condition for **Support**, and then click on \[+ Add component\] to add similar actions/assignments for the other issue types.

comments: author: Prinka Rai
body: Hi Darryl, I have tried this and set the assignee in the transition. Still, the issue is unassigned.

Here is the audit log for the error I just got after I set the rule and tested it.

Rule:

![rule.png](https://community.atlassian.com/t5/image/serverpage/image-id/316181i6544EEBCDE5610EC/image-size/large?v=v2&px=999 "rule.png")

Error Audit log -

![audit log.png](https://community.atlassian.com/t5/image/serverpage/image-id/316182iD2682A8CB9DDB0D0/image-size/large?v=v2&px=999 "audit log.png")


author: Mauricio Heberle
body: I dont think you need three "If-Elses", from you print, seems that only two are sufficient. By your log, you might have a problem in your workflow. Check your conditions and transitions.


author: Bill Sheboy
body: Hi [@Prinka Rai](/t5/user/viewprofilepage/user-id/4107877)

Based on what you described, have you tried changing the rule condition to include all three issue types?

If you have, what is not working as you expected?

Kind regards,  
Bill

comments: author: Prinka Rai
body: Hi Bill, I tried adding all three customer request types, it transit the issue to required status but the issue remain unassigned.


author: Bill Sheboy
body: We would need to see the audit log details to know more, but the likely cause is the two different edits of the issue colliding.

Perhaps try adding a Re-fetch Issue action after the transition and before the Assign Issue action. That will reload the issue data before proceeding in the rule steps.


author: Darryl Lee
body: Ooof - once again, I misread the original question. Didn't see the real problem was the assignment was failing. Sorry.

However, when I was making my nice screenshots, I did see something that might help you: In your **Transition** action, you can opt to set fields there, so maybe you could try that and see if it makes a difference?

![Screenshot 2024-04-03 at 3.06.43 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/316177i26A563AC0452BFEC/image-size/large?v=v2&px=999 "Screenshot 2024-04-03 at 3.06.43 PM.png")

But yes, as [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) mentions - audit logs would be helpful. You might be running into a permissions issue where the Rule Actor doesn't have permission to reassign.