How do i find To Do stories from past date range?

[achal.anikethan]

I want to find all the ToDo stories that were there on a specific dates.

for example: Current date is 30-Sep-2022 and there are around 250 ToDo stories on the sprint board. But I want to know how many ToDo stories were there on 17-Sep-2022 date range. 

Note: Between 11-Sep-2022 and 30-Sep-2022  consider there were 50 stories done.

I tried the query:

project = <My Project> and issuetype in (Story, Spike) and "Team[Team]" in (<My team list>) and status = "ToDo" and (resolved > "2022/09/05" and resolved < "2022/09/09")  

But this doesnt consider the ones which are done and that were not in Done state on that date

[Yuliia_Borivets__SaaSJet_]

Hi @achal.anikethan 

As I understood you need to find stories in To Do status on specific dates including ones that were done. It's hard to filter by JQL in this case. Maybe something like this:

project = <My Project> and issuetype in (Story, Spike) and "Team[Team]" in (<My team list>) and status in ("To Do", "Done")

As an alternative solution, I can suggest Issue History for Jira app developed by my team. Here you can filter by projects, assignees, date ranges, etc. You can choose the dates you need from the calendar.

Add any issue fields you want to monitor changes about (e.g., status). Also, it's possible to choose only specific status transitions.

There is a 30-day free trial, so check if it can help in your case.

[achal.anikethan]

This would have helped me but I can't get authorization to install this plugin.

[Yuliia_Borivets__SaaSJet_]

Maybe you should contact your Jira admin. There are two ways to install it:

•  from Atlassian Marketplace;
•  from Jira admin page.

Here is an instruction:

Installation of Issue History for Jira

[Yuliia_Borivets__SaaSJet_]

If you need more help, please contact our support team at support@saasjet.atlassian.net

[Yuliia_Borivets__SaaSJet_]

Maybe you should contact you Jira admin.
There are two ways to install it:

• from Atlassian Marketplace;
• from Jira admin page.

Here is an instruction:
https://saasjet.atlassian.net/wiki/spaces/SAASJET/pages/16482305/Installation+of+Issue+History+for+Jira

[Yuliia_Borivets__SaaSJet_]

If you need more help, please contact our support team at support@saasjet.atlassian.net

[Sam Nadarajan]

Hello @achal.anikethan

You'll want to change your JQL to say 

status WAS ToDo

or 

status was in (ToDo)

More documentation on this is available here.

Hope this helps!

[achal.anikethan]

This helped to some extent but couldn't match the numbers properly with my earlier snapshot of that specific date result.

I think i am missing something while JQL. Ill try to explore more. Thanks for letting me know the options.

[Mykenna Cepek]

Jira maintains a history of changes to issues. So by reviewing that history log, you can tell when an issue changed from one status to another status. You can see this in an issue, under "History" or "Activity". So for a given issue, you can review the history/activity log and figure it out manually.

However, there isn't anything in the baseline Jira product that lets you do a query like "what status was this issue in on this date?", much less provide a total across all the issues in a project.

Now if your dates of interest align with a Sprint start or end date, then the Sprint Report may have the data you need. The status values in the Sprint Report are (I believe) a snapshot at the moment the Sprint was started or ended.

I suppose their might be a Jira plug-in that does it, but I'm not aware of it off the top of my head (anyone?).

- - - - - - -

I have written some Jira automation rules that run once daily and snapshot information in a project. For your use case, automation in Jira Cloud would make this fairly easy with the Lookup action and the list size() function.

What I do is write the results to the automation Audit Log, and then periodically copy/paste that data into a spreadsheet. That's likely more overhead than you're wanting to do. but it's a way to gather the data you want.

[achal.anikethan]

Automating it is a good option ill explore this and see if it works for me.