Merging three different automation rules to one rule

[Jamshaid]

I have the following three rules that are working separately. I have around 40 type of projects where I will be implementing these rules. Each type of project will have the same sort of logic but key differences will be there. If I stay with this structure, I will need to handle 40*3=120 rules which will become much difficult to handle. I am unable to merge these as if the first one fails, the other two will never run keeping then one after the other in a single rule.

Rule 1

Rule 2

Rule 3

[Bill Sheboy]

Hi @Jamshaid 

Are you trying to merge the logic of the rules into one single rule, and / or...

Are you trying to use three rules to span all of the possible 40 projects, or...

Something else?

And, what are the types of your projects: company-managed, team-managed, JPD, etc.?  That will impact what can be done and how any merging could happen.

Kind regards,
Bill

[Oleksii Melnyk]

Hi @Jamshaid !
Hi! You can use Lookup tables, where the key will be your unique projects and unique values ​​for them.

After that, you can use "if-else" conditions to define your projects and use values from this tables

[Jamshaid]

Thanks. Could you please share some resources regarding this

[Oleksii Melnyk]

I think it must be similar to these screens, but of course you need to add your own actions.

In this case if you have issue created in Project A, it will be cloned with summary CLONE - 1. If in the ProjectB, summary will be with number 2

More details: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-lookup-table/