Jira automation rules linking

[Kavi]

Hi Team,

We have a requirement to auto-assign a specific issue type tickets to specific user based on project. We have around 30+ active projects, hence due to limitation in jira automation (that only 65 components can be added in one rule), was able to achieve partially through two rules with if-else components.

Current rules are as follows:

Rule 1:
if ticket created in project A, it will assign to person John and change status to approve
if else ticket created in project B, it will assign to person Peter and change status to approve
if else ticket created in project C, it will assign to person Andy and change status to approve
if else ticket created in project D, it will assign to person John and change status to approve
and so on..

Rule 2:
if ticket created in project E, it will assign to person Smith and change status to approve
if else ticket created in project F, it will assign to person Chris and change status to approve
if else ticket created in project G, it will assign to person Andy and change status to approve
if else ticket created in project H, it will assign to person John and change status to approve
and so on..
else ticket is not part of any projects, it will assign to person John and change status to approve.

Problem is that part of rule2, it's assigning rule 1's project tickets to person John while executing "else" part of rule 2.

Example: When a ticket is created in Project C, as part of rule1, first it's assigned to Andy, but while executing rule2, it's assigned to John based on else condition.

Could anyone please suggest how to achieve this? For now, I have removed the else part from rule2.

Could not see any option to link both rules.

Thanks,

Kaviraj

[Trudy Claspill · Accepted solution]

Hello @Kavi 

What is the trigger for these rules? Is it using the "Issue Created" trigger?

I would recommend putting an Issue Fields Condition after the trigger of each rule so that each rule will run only when the create issue is NOT ONE OF the projects handled in the other rule.

[Kavi]

Hi @Trudy Claspill 

Yes, trigger was "Issue Created".

Great, thank you so much for your response.

It works as expected now.

Thanks,

Kaviraj