nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sub-tasks not returned by filter, where the sprint is specified

James O_Neill

Hi Folks,

We've a Next-Gen Cloud Scrum Project and are attempting to configure a dashboard widget to display all issues in the current sprint, by issue type and assigned user.

We've found that while stories are being returned fine by my widget, associated child sub-tasks are not.

In investigating this, we've noticed that manually creating a filter where the sprint is included in the query clause, we're only returned stories and not their associated child sub-tasks.

Whereas, removing the sprint clause allows us to see all issue types.

For Example,

project = "<ProjectName>" AND sprint = "<SprintName>" AND status = "In Progress" AND assignee = <UserName> AND issuetype in (Story, Bug, Subtask)

Returns all Stories, but none of the sub-tasks.

However,

project = "<ProjectName>" AND status = "In Progress" AND assignee = <UserName> AND issuetype in (Story, Bug, Subtask)

Returns all Stories and sub-tasks (but includes those items which are still in the backlog).

Is this expected behaviour, and is it possible to return in-sprint sub-tasks, alongside their parent stories?

Accepted answers

Nic Brough -Adaptavist-

It's a known flaw in Jira - whilst the sub-tasks are, of course, in the same sprint their parent is in, the field does not cascade down. So a search can't find them based on sprint.

I've seen a couple of scripted work-arounds - jql functions that can search based on sprint of parent, and scripted fields that pull sprint out on to issues.

All comments

Nic Brough -Adaptavist-

It's a known flaw in Jira - whilst the sub-tasks are, of course, in the same sprint their parent is in, the field does not cascade down. So a search can't find them based on sprint.

I've seen a couple of scripted work-arounds - jql functions that can search based on sprint of parent, and scripted fields that pull sprint out on to issues.

James O_Neill

Cheers Nic, Appreciate the reply.

Am I correct in saying that any scripted work-arounds would require an additional plug-in?

Even if we can get the filters returning the correct values, I'd say it'd be another thing to get these rolling up into widgets.

May have to change the way that we set up the projects.

James

Nic Brough -Adaptavist-

Yes, I've not worked out a way to do this without adding apps to provide the search or field.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud