Parent status should not move

[Teja Bhaghavathi]

Hi Team,

 workflow  is  Backlog- Open- In  progress-Test- Close

 I have set the automation the below automation rules which are working fine.

• Parent goes to IN PROGRESS when the first subtask go to IN PROGRESS

• Parent goes to IN REVIEW when the last subtask goes to IN REVIEW , all the other subtasks are already IN REVIEW, or in TESTS or CLOSED

• Parent goes to TESTS when the last subtask goes to TESTS, all the other subtasks are already in TESTS or CLOSED .
  Problem - when subtask moves from "Close" to "Test"
                                                                   "Test" to " in progress"
                                                                   " In progress" to " Open"
                                                                    "Open  to " backlog"
  Then no changes happen in the status of the parent.
  
  Please help to achieve this.

[Teja Bhaghavathi]

HI @Trudy Claspill ,

I have attached the audit log details along with the rule.
Please check and let me know where I am doing mistake?

[Trudy Claspill]

How did this not perform the way you expected.

The audit log with the timestamp of 09:09:11 indicates the parent of the subtask had its status changed to Test, in accordance with the rule.

The audit log with the later timestamp of 09:13:33 indicates that the second condition you specified for the parent was not met, so the status of the parent issue was not changed.

That second condition is "parent issue status is not in (Test,Closed)". The first run of the rule set the parent to Test. Since the status of the parent is already Test, the condition fails and the parent status is not changed. This is correct behavior for the rule. There is no need to change the parent issue to Test when it is already set to Test.

[Teja Bhaghavathi]

Hi @Trudy Claspill ,

The epic should not move right to left automatically.
When subtask moves from right to left, The parent should not it change status.

As per my criteria PARENT SHOULD NOT CHANGE ITS STATUS when the subtask is moving from left to right through its workflow.

Then what would be the transition for the issue?

[Trudy Claspill]

Hello @Teja Bhaghavathi 

What change do you expect to happen in the parent

when subtask moves from "Close" to "Test"
                                                                 "Test" to " in progress"
                                                                 " In progress" to " Open"
                                                                  "Open  to " backlog"

Do you expect your current automation rules should be handling these scenarios? If so, you will need to show us the details of these rules. We can't help you debug the rules without seeing those details.

Are you asking for help to write additional rules to handle these additional scenarios?

[Teja Bhaghavathi]

Hi @Trudy Claspill ,

What change do you expect to happen in the parent - Parent should not change if subtask moved from "Close to Test"

Are you asking for help to write additional rules to handle these additional scenarios? - Yes

I  need your help in
When - Issue transitioned from "Closed to Test"
For parent- "Transition the issue" 
What I need to select ( Copy from trigger issue,same status (Loop)

[Trudy Claspill]

If the status of the parent issue is currently being changed when a sub-task transitions from Close to Test, and you want to stop that from happening, then we need to examine the rule that is currently triggered when the sub-task transitions to test. Please share the details of any rules you currently have that are triggered when a sub-task is transitioned to Test.

You cannot create a rule to prevent something from being done by another rule. If another rule is causing the parent task to change in this scenario, then that rule needs to be changed. 

[Teja Bhaghavathi]

The above is indicates When subtask is "Test or Close" - Move the parent to "TEST"
But my Criteria is , When Subtask is changed from Close to test( Workflow is moving back from right to left) 
Parent status should not change.
I am not able find the "TRANSITION THE ISSUE TO ?"

[Trudy Claspill]

In the above rule you need to modify the Trigger to specify the starting status of the issue during the transition.

Using that field you can indicate that the rule should only be executed during the transition to Test or Close if the issue was coming from one of the acceptable statuses (i.e. Open, In Progress, Test, Review). Do not include Close in that field, and then the rule will not execute if the issue transitions from Close to Test.

[Teja Bhaghavathi]

When - Issue transitioned 

From- Backlog,open,Inprogress, Inreview,Test

To - ??

For Parent ( What I need to select?

Please help me with full rule. 

[Teja Bhaghavathi]

Hi Team,
Parent should not change if subtask moved from "Close to Test"
In this case what would be the transition for parent?
Please help me with the rule.

[Trudy Claspill]

In this reply I'm only going to discuss the triggers. I'm assuming that the part of your rule that concerns updating the Parent issue is working as you want it to.

For the case where you want something to happen to the parent issue when the sub-task moves to Test or Close except when moving from Close to Test the trigger would be:

When - Issue transitioned 

From- Backlog,open,Inprogress, Inreview,Test

To - Test, Close

For the case where you want something to happen to the parent issue when the sub-task moves to In Progress except when moving from Test to In Progress the trigger would be:

When - Issue transitioned 

From- Backlog,open,Inprogress, Inreview, Close

To - In Progress

If it is possible in the workflow for the issue to move from In Review or Close to In Progress and you want no action taken in that case, then you would remove In Review and Close from the "From" status list.

Generally speaking, if you have an automation rule that you want to run when an issue moves status B but not if it is moving from status C then you specify B in the TO field of the trigger and every status except C in the FROM field of the trigger. 

Apply the above logic to each of the other rules you have.

[Teja Bhaghavathi]

HI @Trudy Claspill ,

PFA image and I am unable to find out the transiition issue.
What Should be the correct option from below?
1.Copy from Issue.
2. Copy from Parent.


3.Copy from Epic
4.Copy from Trigger issue.
5.Same status(Loop)

[Trudy Claspill]

You said your rule worked correctly already except that it executed a transition on the parent issue when the child issue moved backwards through its workflow. If that was truly the case then you only needed to change the trigger for the rule. Nothing else needs to be changed.

Was the "For Parent" section working correctly previously when it was executed? If so then don't make any changes to the "For Parent" section. Put it back the way you had it originally. Only change the Trigger.

[Teja Bhaghavathi]

When - Issue transitioned 

From- Backlog,open,Inprogress, Inreview,Test

To - Test, Close

For Parent

Transition the  issue to :- Copy from trigger /same status as loop 

This is not meeting my acceptance criteria.

[Trudy Claspill]

Are you working with issues in a Team Managed project or a Company Managed project?

To trigger the rule are you changing the status of a Sub-task type of issue or an issue that is a Child of an Epic?

What status did you change the trigger is from and to?

Is the rule executing at all? If so, provide a screen image of the Audit Log for that execution of the Rule.

What is your acceptance criteria?

Is the status of the Parent issue being changed at all? What value did you expect it to be set to? What value was it after the rule completed execution?

I can't provide guidance on the results of a specific scenario without all the details of the scenario;

1. the actions you took against what issue,

2. confirmation that the issue you acted against has an issue that qualifies as its "parent" based on the logic used in the Rule,

3. what you expected to happen,

4. what actually happened,

5. the details of the rule that ran (preferably a screen image of the rule)

6. the details from the Audit Log for that execution of the rule.

[Teja Bhaghavathi]

Are you working with issues in a Team Managed project or a Company Managed project? -Our Project is "Company managed project"

To trigger the rule are you changing the status of a Sub-task type of issue or an issue that is a Child of an Epic?-  changing the status of a Sub-task type of issue 

What status did you change the trigger is from and to-  As per your reply I have created the rule( PFA rule )

Is the rule executing at all? If so, provide a screen image of the Audit Log for that execution of the Rule. - I have created the rule as per your reply and the status is "SUCCESS" but I am bit confused with "Transition" It is not meeting my acceptance criteria

What is your acceptance criteria?- My workflow is 
Backlog- Open-In progress-In review-Test-Close

At any point in time, if a subtask goes from right to left, no changes happen in the status of the parent.

Parent goes to IN PROGRESS when the first subtask go to IN PROGRESS

Parent goes to IN REVIEW when the last subtask goes to IN REVIEW , all the other subtasks are already IN REVIEW, or in TESTS or CLOSED

Parent goes to TESTS when the last subtask goes to TESTS, all the other subtasks are already in TESTS or CLOSED .

Is the status of the Parent issue being changed at all? What value did you expect it to be set to? What value was it after the rule completed execution?- The parent should not change its status when the subtask of  an issue moving back through its workflow (For example, If I move subtask to "Close " - The parent should move to Close
                         If I move same subtask from "Close to "TEST"- expected behavior The parent should in "CLOSE"

PFA images for my other rules

[Trudy Claspill]

Hello Teja,

I know this is a lot of back and forth conversation. I am hoping that this will ultimately help you learn how to debug your Automation rule so you will be able to apply what you learn to your other rules. In my opinion this is a better path than me just writing the rule for you without you understanding why your rule did not work as expected.

Let us look at just one rule at a time. Let us start with the rule that executes when you change the Status of a Sub-task to Test or Close.

Show us an image of that one rule. Show all the components in that rule.

What was the actual, specific value Status of the Sub-task before you changed it? For example, "The Status of the Sub-task before I changed it was Close."

What was the actual, specific value Status of the Sub-task after you changed it? For example, "The Status of the Sub-task after I changed it was Test."

What were the Statuses of all the other Sub-tasks under that Parent issue?

What was the actual, specific value Status of the Parent issue before you changed the Sub-task Status? For example, "The Status of the Parent issue before I changed the Sub-task was Close."

What was the actual, specific value Status of the Parent issue after you changed the Sub-task Status? For example, "The Status of the Parent issue after I changed the Sub-task was Test."

How exactly did this not match your acceptance criteria? For example, "I did not want the Status of the Parent issue to change in this scenario because I don't want the Status of the Parent task to go backwards in its workflow regardless of how the Sub-tasks change."

Please show the details of the Audit Log for the rule execution when you made that specific change to the Sub-task Status so I can review which pieces of the Rule executed. The rule execution status may be SUCCESS, but that is not enough information to tell me which pieces of the rule executed. If you click the Show More link to the right of the rule execution status it will show you details of the steps executed. Example:

Provide ALL the same information as above for a scenario where you changed the Status of a Sub-task to Test (or Close) and your acceptance criteria was met. For example, "I changed the Status of a Sub-task from In Progress to Test and the status of the Parent issue did not change (remained In Progress), and this met my criteria because there was still a Sub-task that had a status that was not Test."

With ALL that information I can write back walking you through how the logic of the rule was applied to the specific scenarios you executed, help you understand why it did not work as you wanted, and help you identify how it needs to be changed.

[Trudy Claspill]

Hello @Teja Bhaghavathi 

You are not providing the answers to all the questions I am asking.

Regardless, I am going to provide you with an example.

For this rule:

Parent goes to TESTS when the last subtask goes to TESTS, all the other subtasks are already in TESTS or CLOSED .

First I'm going to restate the same thing in the order you would develop the rule:

(A) WHEN: a subtask transitions to Test
(B) FOR: the subtask's parent
  (C) IF: all the subtasks are in a Status of Test or Closed
  (D) AND IF: the parent issue is not in a Status of Closed
  (E) THEN: transition the parent issue to a Status of Test

Here is the rule:

(1)TRIGGER: Issue Transition
     - From Status: Open, Backlog, In Progress, In Review
     - To Status: Test
(2)CONDITION: Issue Fields Condition
     - Field: Issue Type
     - Condition: equals
     - Value: Subtask
(3)BRANCH RULE/RELATED ISSUES: 
     - Type of Related Issue: Parent
  (4)CONDITION: Related Issues Condition
       - Related Issues: Sub-tasks
       - Condition: All match specified JQL
       - JQL: status in (Test, Close)
  (5)CONDITION: Issue Fields Condition
       - Field: Status
       - Condition: is not one of
       - Values: Test, Close
  (6)ACTION: Transition issue
       - Destination Status: Copy from Trigger issue

Mapping the rule statement elements to the constructed Rule:

(A) is handled by (1) and (2)

(B) is handled by (3)

(C) is handled by (4)

(D) is handled by (5) - this is what prevents the parent issue from moving right to left

(E) is handled by (6)

I recommend that you create one Automation Rule per Sub-task status.

Please try to extrapolate the other rules from this example.

If you need additional help you must

- ask about only one scenario. Trying to answer your questions about multiple rules at once is not turning out to be productive.

- Provide a copy of your rule.

- Explain the scenario that is not working the way you expect; i.e. The parent issue is in Close. All the sub-tasks are in Test or Close. I changed a sub-task from Close to Test and the parent then changed from Close to Test. I don't want the parent to change from Close to Test in this scenario.

- Provide a copy of the Audit Log for the execution of the rule that did not perform the way you wanted.