Change Story status based on part of the sub-tasks match the condition

Igor Koji

I'm using Story (parent) eg 'Story' and linked subtasks (child). Each Sub-task has an issue type (A, B, C) eg Task1 (A), Task2 (B), Task3 (C).
My statuses: To do, Doing, Done.

  I would like to know how to configure so that:
  - If 'Task1 (A)' and 'Task2 (B)' are in Done status, then the Story Status changes to Done, regardless of whether Task3 (3) Status is in Done status or not. 

Change Story status based on part of ( neither "ALL" nor some") sub-tasks match the condition

 

Thank you

Andy Heinzer

Hi Igor,

I understand that you're using automation in Jira Cloud and want to be able to specifically close the parent issue when two specific subtasks are done, regardless of the status of the third subtask.

In order to make this work, we need some way to distinguish these two subtasks apart from that third one.  If all of these issues appear identical, it won't be easy to manage this. 

The way that I think might help achieve this would be actually to change that 3rd task to be a completely different issue type.  Jira let's you create your own issue types, including having multiple subtask types.  Just by having this third task have a unique issue type name apart from sub-task can help here.  Say you call that task an issue type called 'optional' or 'extra' or anything apart for your current issue type names.

That way you can use automation to make a JQL query condition such as

parent={{issue.parent.key}} AND issuetype="sub-task" AND status=Done

This way when the trigger activates, all the issues that are of issuetype='sub-task' and done status of that issue can then transition that parent issue.  Your 3rd issue wouldn't have to match that since it would have a different issuetype.

 

You don't have to create a whole new issuetype to achieve this.  You could do something as simple as just creating a custom field value for all these 3rd issues and give the other pair a different value.  As long as JQL can distinguish the issues apart in some way, we can use that to create automation conditions in the manner I think you want here.

Let me know if you have any questions or concerns about this approach.

Cheers,

Andy