Automation Rule Issue

[Jatin Bansal]

I don't know why it is showing No actions performed always 

The rule is written right but it is not working as expected as it is not doing any action

The screenshot is attached below

Can you please help.

[Trudy Claspill]

We need information about the issue(s) triggering the rule. If the issue triggering the rule does not have a parent Epic then there will be no actions executed.

You don't have a Condition after the trigger, so the rule could be getting triggered by Subtasks, which have no parent Epic, or by Epics, which also don't have parent Epics.

If the image you posted doesn't show all the components of the rule, please post additional images that do show all components of the rule.

Also, if you think a triggering issue does have a parent Epic, can you show us a screen image that shows us the triggering issue does indeed have a parent Epic?

Is this rule running against a Team Managed project or a Company Managed project?

[Jatin Bansal]

Hi @Trudy Claspill 

1. The rule is running against a team managed project 
2. The issue triggering the rule does have a parent epic but, the situation is this:

For subtask- You can change the status from Dev-to-do to Dev-In-Progress when start date, due date and original estimate are set

For EPIC- You can change the status from Dev-to-do to Dev-In-Progress when start date, due date and original estimate are set

For story- You can change the status from Dev-to-do to Dev-In-Progress when start date only is set

How does this happen?

And how to resolve this.

[Trudy Claspill]

Hello @Jatin Bansal 

I constructed a rule like yours in my own Jira for a Team Managed project.

I get the No Actions Performed message if the rule is triggered by a change of Status for an issue that is not a direct child of an Epic. That occurs when the issue is a Subtask that is a child of one of the Child Issues of the Epic.

This rule will transition the Epic only if the issue that triggers it is a direct child issue of an Epic.

Can you show us an image of issue PRJCT-257 showing enough information to show that it is a direct child of an Epic issue?

If the issues that are changing Status to Dev-In-Progress are not direct child issues of an Epic, then no actions will be performed in the rule.

If that is not how you want the rule to behave, please detail what you do what to have happen in the following format:

1. When <this action> happens 

2. Where the trigger issue matches these Conditions; i.e. issue type <Z> with field <X> set to <value> and field <Y> set to <value>

3. Then for <this type of related issue>

4. Where the <related issue> matches these Conditions; i.e.  field <X> set to <value> and field <Y> set to <value>

5. Execute <this action>