Show parent issue related to sub-tasks
Issue #3
resolved
In our team (and I believe in many others, too) we use sub-tasks to accomplish Stories and Bugs, and usually all the work happens in them. In the issues interface it shows them, but I can't know to what parent issue they are related even when opening their tab, and then I'm having to go to the web browser every time.
I would like see, by default or through an option in extension settings, the sub-tasks grouped by their parent issue, both in "Open Issues" and "My Issues", as well as in "Custom JQL", even if the parent issue wouldn't be displayed in the filter.
Something like this:
Comments (7)
-
reporter
-
Account Deactivated
- changed status to resolved
@laurentvox Thanks for the feature request. We have released a new version of the extension (1.0.2) where we added this feature. Please try it out and re-open if needed.
-
reporter
Hi @pbusam , thank you for considering this feature, I had the chance to test it here!
But I found one issue: if I have a JQL that would show me only some of the sub-tasks contained in a Story, it shows me those under the Story now, but is also showing me the other sub-tasks of that Story that would be filtered out by the JQL.
In Jira, using Quick Filters in a Kanban board, for example, in this same scenario it would only show me the sub-tasks that match the JQL criteria and the Story these sub-tasks belong. Is it possible to have the same behavior described above in the extension?
Again, thanks for prioritizing this feature!
-
reporter
- changed status to open
-
Account Deactivated
A new version of the extension has been released v1.1.0 which tweaks how the subtasks are displayed. Can you update and check if it looks good?
-
reporter
Hi Pramod. Yes, I had the chance to test and now it seems that it is working really well, good job! Thank you for your attention on this Pramod!
-
Account Deactivated
- changed status to resolved
That's awesome!! Thanks for the feedback.
- Log in to comment
Any response on this one? Or at least something that would help with this problem, because the Jira part of the extension is almost unusable for us if the sub-tasks will be just scattered around, and we still have to go to browser to manage it.