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; } } }

A Bug in Jira's Automation - When all Subtasks are done, Move parent (Story) to done

Mostafa Hegazy

So I have a current issue with Jira's automation. I think it's a Bug.

First we have Jira's normal "Subtask", and that when I created the automation for it all goes smooth and well, as so:

However, I have created another Subtasks issue type called "Test Cases" (with it's own workflow) and when both subtasks are created within the same story, the "related issue condition" within the automation rule always fails even when I use JQL within the "related issue condition" so that I can specify exactly "Subtasks" and not "Test Cases" Subtasks , Like so:

Please let me know if you can help me with this situation or if it's a current issue within Jira

Accepted answers

All comments

Sachin Dhamale_o1c5zi

@Mostafa Hegazy ,

In the "Related issue condition" have you try with following parameter. In the Matching JQL -

status="DONE" only.

Releted Issue Condition.png

Mostafa Hegazy

that's exactly the first try, and it works perfectly is there is only Jira's default "Subtasks", but when I added a new subtask "Test Cases" (I created it). it always fails.

I feel like Jira can't couldn't cope with the new subtask, if it is or isn't a subtask so it just fails.

So I even created a JQL within the "Related issues" field as so:

issuetype = Sub-task AND issuetype != "Test Cases"

Still doesn't work!

Alex Koxaras -Relational-

@Mostafa Hegazy hi,

I've tried your rule and it works just fine:

parent rule.png

I've got 2 different subtask issue types. The first three are sub-tasks, whereas the fourth one is a "test case" subtask. The rule is triggered with every subtask move to done. And when I finally move the "test case" to done, it's also moves the parent.

Sachin Dhamale_o1c5zi

@Mostafa Hegazy ,

In the Matching JQL Can you try

issuetype in (Sub-task, Test Cases) and status = "Done"

Because you wanted to treat "Test Case" as subtask

Mostafa Hegazy

Actually not, I wanted that only once all "Sub-tasks" subtask issue types is done, then the story to transition to "Ready for Testing", NOT when "Test Cases" Subtask issue type to transition to done as well.

They both have different workflows, and different roles assigned to each

Mostafa Hegazy

Yes this is the first scenario that goes smoothly without any issues, but if you tried creating a new subtask issue type, and adding it to the same story as that subtask, it will not work. it will fail

Alex Koxaras -Relational-

@Mostafa Hegazy that's what I did in the scenario above. I have two different subtask issue types: Subtask and Test Case. They both work fine.

I would suggest that you share a screenshot of your rule's log
A screenshot of your issue type scheme
And the complete steps you are taking

Mostafa Hegazy

I'll send you screenshot, but I don't want when all subtasks issue types are done then parent is done.

I want when ONLY "subtasks" subtask issue type is done, then parent is done.

So keep the "Test Cases" subtasks, "To-do" or "In Progress".

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