Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to search for pending issues at the beginning of the Sprint using JQL

David Leal
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 1, 2019

We started the Sprint on: 2019/1/22 and we would like to know how many issue we committed at the beginning of the Sprint. We are using the following query:

project = ATHP AND Sprint = 1113 AND (status was not in  (DONE, "BUILD COMPLETE") AFTER "2019/01/21" ) AND (status was not in  (DONE, "BUILD COMPLETE")  BEFORE "2019/01/23")

The query returns: 50 issues.

We have the following issue types: epics, stories, features, task and sub-tasks. With the following statuses:

  • Epic, Task and sub-task: TO DO, IN PROGRESS and DONE
  • Story: TO DO, IN BUILD, BUILD COMPLETE, IN QAT, REWORK and DONE.

In our board the left-most column has TO DO  status and the right-most column considers the statuses: BUILD COMPLETE (for story) or DONE (for task, sub-task and epic)

Therefore every thing that is not in BUILD COMPLETE or DONE is work pending. That is what are we looking for. Is it the correct way to obtain this information?

When I look into the burndown chart, at the beginning of the Sprint with ID: 1113 we have: 50 issues, but the issue count is: 47. The burnup informs that the work scope at the beginning is 47. In both cases we have selected the option: Issue count.

The following query (only sub-tasks):

project = ATHP AND issuetype in (Sub-task) AND Sprint = 1113 AND (status was not in  (DONE, "BUILD COMPLETE") AFTER "2019/01/21" ) AND (status was not in  (DONE, "BUILD COMPLETE")  BEFORE "2019/01/23")

Returns 8-subtask, 

Running a similar query for:

  • epic the result is 0
  • story the result is 5
  • task the result is 12
  • feature the result is 25

In total for epic, story, feature, task and sub-task there are: 50 issues, i.e the same result as the total number issues the burndown charts informs. Then what is the issue count in this chart?

If We try to compute only: story, feature and task in order to have the issue count of 47 from the durndown or burnup, using this query, we don't get 47:

project = ATHP AND issuetype in (story, feature, task) AND Sprint = 1113 AND (status was not in  (DONE, "BUILD COMPLETE") AFTER "2019/01/21" ) AND (status was not in  (DONE, "BUILD COMPLETE")  BEFORE "2019/01/23")

instead the result is 42 not 47. Which is logical, because we have 8 sub-tasks.

Are we missing something?, Is is the correct way obtain the issues pending at the beginning of the Sprint? Is there any better way to obtain this information?

How can we get the same issue count as in the burndown chart?

Thanks in advance

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events