Show subtasks when filtered by Sprint and by Assignee

[Lova Ranaivoson]

Hi~ ☀️

Our team is using Jira - mainly for the first time for most of us - and we're trying to find ways to help them using it easily.

We have the Free Plan since we just hit the 10-persons size, and divided our work between Epics, Tasks and Subtasks.

To help our members using Jira, we wanted to give them direct access to their Subtasks, so that they don't have to navigate through the entire project.

Problem is: when we want to filter the Subtasks by Assignee by Sprint, the Subtasks disappear!

Like this (sorry the pictures have some French in it, but I assume Jira has the same setup in every language!):

Case 1: Filter by Assignee:

Result:

It works, yay 🥳

Case 2: Filter by Assignee by Sprint

Result:

Aaaaah it all disappeared 🤯

(Note: The Assignee choosen in this example did have Subtasks in Sprint 6, and the situation is the same when we change Assignees)

Question is: how can we solve this? What did we do wrong?

Thanks for your help!

[Hannes Obweger - JXL for Jira]

Hi @Lova Ranaivoson

welcome to the community!

I just tried this on my site and can confirm what you seeing: For sub-tasks from team-managed projects, JQL searches based on sprints don't seem to work. This looks like a bug to me, and should probably be raised with Atlassian.

It's worth noting that sub-tasks are a bit special, in that they always "inherit" the sprint from their parent issue. I could imagine that our bug is somehow related to this this special behaviour.

Best,

Hannes

[Hannes Obweger - JXL for Jira]

... and just to add to the above: If you're open to solutions from the Atlassian Marketplace, your use case would be easy to solve using the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of advanced features, including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

Plus, filtering sub-tasks by their sprint works as expected, for company-managed as well as team-managed projects. This is how it looks in action:

Any questions just let me know,

Best,

Hannes

[Danut M _StonikByte_]

Hi @Lova Ranaivoson,

Is your sprint and the sub-tasks in a team-managed project?

If so, unfortunately it is not possible to filter the sub-tasks by sprint at the JQL level due to a known Jira bug/limitation:  https://jira.atlassian.com/browse/JSWCLOUD-25893.

So I'm afraid that it is not possible to achieve what you want at the JQL level.

For facilitating the easy access to sub-tasks, my advice is to use a different approach. For example, you could make the sub-tasks visible to the users by displaying them on a dashboard by using the Team Wallboard gadget offered by our Great Gadgets plugin.

This gadget displays the contents of an agile board, including the sub-tasks (the ones in yellow color). And you can display swim-lanes by assignee, epic or story and lets you apply the boards quick filters.

Danut. 

[Cristian0791]

Hi Lova,

Try to switch from Basic to JQL and you can use:

project = TS and issuetype = Sub-task and status = "To Do" and assignee =5badf8fe653ec8726d2a2018 and Sprint = 34

You should replace:

Project from TS to WK

assignee with 5badf8fe653ec8726d2a2018 to your own ( it will autocomplete)

Sprint with your own ( you will chose from a list)

Hope this helps.

[Lova Ranaivoson]

Just tried, unfortunately it doesn't work... 🥹

Thanks for trying!

I also discovered here (after posting my message...) that even if the field "Sprint" appears in the Subtasks, it looks like the filter doesn't apply on them, and only on the main Tasks they belong to.

But it also seems weird from Jira to show a field appearing, and not giving the ability to simply filter those Subtasks by Sprint?...

[Cristian0791]

Hi Lova,

I am able to achieve the filtering using the same JQL.

Maybe try to change the "New View Search" to the "Old View Search"