This is an answer rather than a question.
I'm in the Cloud and I need a way to see issues that do not have subtasks, for a set of specific parent and subtask issue types. There is no nice way to use the out-of-the-box filtering or plugins in the Cloud to find issues with subtasks.
What I did:
It's simple but it works for me. Hope it meets someone else's needs, too.
Good "question". Just one point. How do you search for issues with more than 1 subtask. As I understand this if you create two subtasks each of them has in "hasSubtasks" the value 1. And this value is copied twice to the parent (but the second copy overwrites the first one), so the parent has value 1 in that field, or?
Is there any way you can attach a screen shot of what the filter produces?
Also, what made you create this solution?
I have issues grouping our subtasks with the parent. As everyone knows, when you create the subtask it uses the next number sequence and does not associate that subtask to the parent number. example - parent ticket PROJ-89 with subtasks tickets of PROJ-124, PROJ-138, PROJ-139.
It would be nice if it would truncate the parent number for the subtask - example - parent ticket PROJ-89 with subtasks tickets of PROJ-89.1, PROJ-89.2, PROJ-89.3
What made me want to do it was that we had no way of knowing if we had assigned subtasks. One of the issue types we have is a document issue. We have a subtask approval/rejection workflow for those issues. It's possible for someone to set document (parent) issue to "ready to approve" but not have added the approval (child) subtasks for each person to do their approval. (For example, you would add a separate document approval subtask and individual assignee for each person who should sign off on the document.) Rather than clicking on every issue that is ready to approve to see if it has child approval subtasks, I can see it easily based on the subtask count. I can also see if it doesn't have enough subtasks, meaning the didn't assign the requisite number of approvers. Regarding your other idea of the parent-child tasks having linked numbering, this really isn't an issue for us right now but I can see lots of reasons it would be helpful to other things I'd like to do with JIRA in the future.
Sigrid - Thank you for the quick response and reasoning for your changes. The explanation leads to many additional thoughts on my side of what we could be doing with JIRA for our organization. I have place this information on my list of follow ups and business model modifications.
Thank you again!
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG