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.

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.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Accepted answers

All comments

Trudy P 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 P 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 P 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

Parent moves to Test.PNG 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 ?"

Teja Bhaghavathi

Hi @Trudy P 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?

Teja Bhaghavathi

Parent status is moving.png

HI @Trudy P Claspill ,

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

Trudy P 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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud