Created the automation rule with if else flow ,the first if matches used action assign user is not working ,after else if is working.my concern is i am created the rule and assign user
Hi @Abilash, Welcome to the Atlassian Community! From your audit log, the Assign work item action itself appears to be working correctly. In the 13:34:07 execution, Jira shows, If block → The following issues did not match the conditionLISM-1799 It then continues through the Else-if blocks until one matches, and only then executes Assign work item. That is the expected behavior of an If/Else chain. So I would focus on your first condition, Status equals Sales Approval. Your trigger is Work item transitioned, and the audit log screenshot shows LISM-1799 as In Progress. If the item was not actually in Sales Approval when the condition was evaluated, the first branch will correctly be skipped. Since each branch appears to represent a particular approval/status, an even cleaner setup would be to configure the Work item transitioned trigger for the relevant destination status where possible, or keep the generic transition trigger and verify each If/Else status condition carefully. I would also expand the first If block in the audit log and confirm exactly which status Jira evaluated. Based on the screenshots, this looks like a condition mismatch rather than an assignment failure.
Regards, Gor
Hi @Gor Greyan ,Thanks for your response.the same work flow used in my trail jira its working,not understanding exactly where i am missing ,if possible could you make automation rule according to my requirement when ticket created assign to sales user and after sales user approved ,then automatically assign to executive user and after executive user approved,status transit to inprogress it assign to other user,below is the work flow
Hi @Abilash,
Thanks, the workflow makes the requirement clearer. You can handle this with one automation rule, you don't need separate rules. Configure it like this. Trigger: Work item transitioned to the Statuses - Sales Approval, Executive Team Approval, In Progress Then add an If / else block: IF Status = Sales Approval → Assign work item to Sales user ELSE IF Status = Executive Team Approval → Assign work item to Executive user ELSE IF Status = In Progress → Assign work item to the user responsible for In Progress This matches your workflow, so Sales Approval → Executive Team Approval → In Progress. The key point is that the condition must check the current status after the transition. For example, when Sales approves the request, Jira transitions it to Executive Team Approval; at that point the Sales Approval condition should not match. The Executive Team Approval branch should match and perform the assignment. Your earlier audit log actually shows this If/Else mechanism working, Jira skipped the conditions that didn't match and executed the assignment under the branch that did match. Also verify that each selected assignee has permission to be assigned work items in the project.
Abilash, the single rule still misses the first stage. Your create transition lands straight in Sales Approval, and "Work item transitioned" doesn't fire on create, so the Sales Approval branch has nothing to fire on. That's the original symptom.
1. Rule one, trigger "Work item created", action Assign work item to the sales user. That's it.
2. Rule two, trigger "Work item transitioned", then If status equals Executive Team Approval assign the executive user, Else-if status equals In Progress assign the delivery person.
No Sales Approval branch in the second rule. Create already covers it.
Hi @Mihai_LeanZero , Already created the same its working now.but have one question in progress we should mention request type equal condition?,as checked that when other request type status come to in progress its automatically assigning to that person. Thanks for response.
Yes, add it. Put a Work item fields condition right after the trigger, before the If/else: Request Type equals your request type, picked from the list. Sitting there it covers both branches.
Same condition in rule one too, otherwise every new request of any type gets assigned to the sales user.
It looks like you're new here. Sign in or register to get started.
