How to create automation rule for each condition matched

[SJ]

Hi, I'd appreciate experts' help on this as I've been wracking my brain over it. 

Project: company managed
Issue types in scope: Epic and Task
Link type: Task “blocks” Epic
Task statuses: To Do, In Progress, Complete
Task Story Points: 0, 1, 2, 3
Epic custom statuses: Red, Amber, Green, Black (RAG + B)
Trigger: When a Task updates its Story Point field.

Target Epics to evaluate:
1. From the Task that triggered the rule, find all Epics that this Task blocks. Note that a task may block more than 1 Epic, so for each such Epic, run the evaluation steps below independently.

2. How evaluation runs on each trigger:
- For each of those Epics, fetch the full set of Tasks that block it.
- Read the Story Points of ALL those blocking Tasks, not just the task that initially triggered.
- Ignore SP 0 during risk evaluation, except for the “all zero” check.
- Decide the Epic’s RAG using the rules below, then transition the Epic to that status.

In this model, a Task’s workflow status does not affect the RAG calculation. Only Story Points matter. 

Definitions
For the set of Tasks that block the Epic:
* c1 = count with SP 1
* c2 = count with SP 2
* c3 = count with SP 3
* n = c1 + c2 + c3 (all non-zero SPs)
* Zeros are ignored for n, except when every blocker is zero.

Decision rules and precedence
Evaluate in this order. The first match wins.
1. Black
All blocking Tasks are SP 0.
Equivalent: n = 0.

2. Green
All non-zero blocking Tasks are SP 1.
Equivalent: c1 > 0 and c2 = 0 and c3 = 0

3. Red
SP 3 is the most common Story Point value among all non-zero blockers.
Equivalent: c3 > c1 and c3 > c2

4. Amber
Anything else that is not Black, not Green, and not Red.


===
My (faulty) solution: 



What I've built so far:

[Bill Sheboy]

Hi @SJ -- Welcome to the Atlassian Community!

First thing: your question seems to indicate you are on a Free license level.  If that is so, please note there is a limited number of rule usage executions per month, and so the rule shown likely will only succeed if you have very few work items.

Back to your question...

If you compare your rule outline to the rule you created in the editor, you will observe the If / Else condition block cannot be used inside a branch.  However, the converse is possible: using a branch within an If / Else condition block.

Please pause to consider how your rule might be restructured to account for this limitation and implement your logic.  For example:

• When Tasks are updated, their story point values could be aggregated in the parent epic and then that value used, or...
• Conditional expressions (perhaps with lookup tables) rather than condition components could be used to determine the target status for the transition
• etc.

Kind regards,
Bill

[Marc - Devoteam]

Hi @SJ 

Welcome to the community.

Whenever you ask for help with an Automation Rule it will help us to help you if you provide:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

These questions are not for not willing to help, but to have community members understand on how automation works.

[SJ]

Thanks Marc- appreciate the feedback. I've updated my question with the details!