I’m using a JQL filter based on the updated field.
In the normal case, I query standard issues only for a project. (subtasks field is included)
When a timestamp is available, I query both standard issues and sub-tasks and apply an updated-after timestamp filter.
My question is about the following scenario:
If only a sub-task is updated after the given timestamp, while the parent task itself is not updated, is there any way (using JQL and/or the Jira REST Search API) to return the parent task (standard issue) and include its subtasks list, instead of returning the sub-task?
In other words:
Is this behavior supported natively in Jira (Cloud and/or Jira Data Center), or is it a known limitation of JQL?
Thanks for any clarification.
Hi @mustafa_salihi ,
I'm not quite sure I follow here, but here it goes.
From what you've described I've managed to find one open suggestion that might be relevant: JRACLOUD-18839: Create a JQL functionality to filter the sub-task / child issue for a field value of the parent issue
Now, for the use case itself, the first thing that came to my mind was what about automation? 🤔
For example, you could use trigers such as work item transitioned or scheduled (if you're checking that timestamp field on the sub-task) and then lookup for parent work item and all sub-tasks under that parent item.
Once you have that, you can send that list to Teams, email, or some other channel you like.
That's just an initial idea - it surely needs some work around it.
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.