JQL to obtain the sub tasks created in the last or current sprint

[Irvin Mendez]

Hi, I'm looking a JQL to obtain only the tasks created in the last sprint, when filter the tasks by sprint I get all the task include the carry over tasks, but I need only the created in this sprint.

I'm ussing this JQL but 

type = Sub-task AND project = STR AND reporter in (irvin.mendez) and (created >= "2020/06/03" AND created <= "2020/06/16")

[Andy Heinzer]

Hi Irvin,

I understand you are looking to find in JQL all the subtasks created during a sprint.  I am afraid your JQL explain does not indicate if the subtask created are part of any sprint or not.

If this sprint is in a next-gen project, then you should first be aware of this bug JSWCLOUD-18398 : Unable to search for sub tasks in a sprint on a next gen project.  Next-gen project based sprints currently won't be able to return subtask via JQL just yet due to this bug.

However, if this is a classic project, then you should be able to see that with something simply such as:

type=sub-task and sprint=4

With the sprint field, you can actually use the sprint name, but many times the autocomplete will change this use the id number of that sprint in question.  In my example, my "Sample Sprint 3" had an id number of 4 which serves to return all issues in that sprint.

You could also restrict this further to find the ones created during that time frame, such as with

type=sub-task AND sprint=4 AND created >= "2020/06/03" AND created <= "2020/06/16"

That should then be able to show you all the subtasks in that sprint that were created within the desired date range.   I removed the project and reporter fields from your query since sprints can technically contain issues from other projects and have different reporters.

I hope that helps.

Andy

[Irvin Mendez]

Hello Andy,

Yes, it is a classic project. but the problem with this query is that it also returns the tasks generated in a previous sprint that were assigned to the current sprint. and I don't understand why, since I'm indicating the time span.

[Andy Heinzer]

Ah, thanks for clarifying.  JQL queries on the sprint field are not historical in nature.  JQL is typically only able to show us what Jira issues are in that sprint right now.  The created dates will restrict the results to issues created within that timeframe, but not necessarily to those only created in sprint itself at that time.  Perhaps you're running multiple sprints in parallel.  That could also potentially explain the behavior you are reporting here.

If you were not running parallel sprints, then Jira Software tends to restrict the board to only a single active sprint at a time.  That could better help to isolate the issues in this case, but I'm not sure there is a sure fire way to determine which subtasks were certainly created when in a specific sprint.

[Irvin Mendez]

Thanks for the info I didn't know that.