URGENT! Subtask based on parent issue Summary?

[Dionei Piazza]

Using a JQL filter (without plugins), how can I get all subtasks based on the Summary field of the parent issue?

I don't want to use plugins

[Jack Brickey · Accepted solution]

You can’t return the subtasks in the search results but consider...

• search for the summary and return the parent(s). From there you can drill down into the parent and view subtasks
• Something to try - using a manual automation find the parent and add a label to the subtasks. Follow that with using JQL to find the label

[Dionei Piazza]

Thank you @Jack Brickey 

So, following your first tip: "search for the summary and return the parent(s). From there you can drill down into the parent and view subtasks", I would need to do this manually every time. Am I right?

[Jack Brickey]

correct. in your original post there wasn't any details around your use case so I took a more direct occasional need approach. Can you elaborate on your UC so that I might ponder other solutions?

[Dionei Piazza]

Right! I think it's ok @Jack Brickey  

I had already thought about the option of an automation to set a label.

My scenario is:

1 - We have subtasks that are linked in a parent Task where the Summary ever will contain "Plantão dd/mm/yyyy".

2 - At a certain cadence, we want to export these work items informations to understand the cause and propose improvements.

3 - So I would need a JQL that searches for all subtasks whose parent issue summary is "Plantão".

So I thought of a JQL filter to be run by the team administrator. After running the filter, it would export it to a spreadsheet.

[Jack Brickey]

This is one of those "why isn't this possible today" features that has been missing forever and wish it would get added. :-(

Here is what I suggest. If you can qualify your use case such that the parents, where you are interested in the sub-tasks, will always have some reliable details (summary text, field, label, etc) then consider Automation like below...

Trigger - Issue created

Condition - JQL --> type = sub-task

Condition - JQL for the parent where the summary text, field label, etc. = xxxxx

Action - edit issue and add label

Now you can JQL on type and label --> type = sub-task and label = yyyy and ????

the ???? needs to further qualify to pick up only the sub-tasks your are interested in not say the ones you have previously processed.

Hope this helps!