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; } } }

Why SubTasks can not search by Sprint?

Ulysses Kao

When I try to search sub tasks via JQL

if I use JQL below

project in (xxx) AND issuetype in subTaskIssueTypes() ORDER BY key ASC, Rank ASC

I can search my sub task out.

But if I add "Sprint"
project in (xxx) AND issuetype in subTaskIssueTypes() AND Sprint =yyyy ORDER BY key ASC, Rank ASC

It always shows nothing.

I also tried

project in (xxx) AND issuetype in subTaskIssueTypes() AND Sprint is not EMPTY ORDER BY key ASC, Rank ASC

it still shows nothing.

Why is that?

Is it a bug?

Accepted answers

All comments

Nic Brough -Adaptavist-

I hesitate to call it a "bug", as a bug is software doing something unexpected and wrong. This behaviour is not unexpected and there's some argument about it being "wrong". My opinion is not quite that it is "wrong", but very much "it's very unhelpful and confusing, and there's no good reason not to change the way it works".

A sub-task is a part of its parent issue. Not a linked adjunct or distant relative, it's part of the issue. So there are some things that would be nonsense if they were separated from the issue. Sprint is one of those. Sub-tasks, because they are a part of an issue, are implicitly and logically in whatever sprint the issue is in.

So a perfectly reasonable thing for us humans to do is ask "what sprint is it in", and the answer should be "the sprint my parent is in, which is <x>"

But Atlassian have neglected this. Sub-tasks simply don't show sprints.

I think they should. Obviously, not a field you can edit, but we really should be able to ask "what issues are in this sprint" and get all the stories and sub-tasks (by virtue of them being a part of a story in the sprint)

Ulysses Kao

Yes, you may right.

But I still need to search the all sub tasks in sprint, like you said, they are still a part of story in the sprint, I still need to control their effect and story point.

So....will Atlassian fix (or said as modify) it?

or give me another way to do it?

Nic Brough -Adaptavist-

I do not think Atlassian are going to do anything soon to fix this reporting problem, which is mildly annoying.

I don't mind that I have to copy and paste a short script into most systems, but it would be nice to not to have to (and not have to worry if the customer has one of the apps that can do it). Another option is to implement a sensible JQL function to return the sub-tasks as well.

But I am not sure what you are looking for when you say "control their effect and story point". Sub-tasks do not have story points, and I do not want to guess what "control their effect" is.

KAGITHALA BABU ANVESH_z1zl10

Daniel Ebers

This is especially interesting. I'd like to add a detail question if you don't mind.
Kagithala shared a screenshot later (below this reply) which, to a surprise, shows a working output to the query.

So I went to my cloud instance and played in a test project and it also seemed to work?! Now I do not understand anymore the topic.
Could you please confirm there is some difference to what Ulysses asked initially or is there some "magic" happen (in my cloud instance not a single App is deployed, tbh it is just a playground)?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud