Filtering Issues - Pull through correct tickets to dashboard

Question

Currently we have dahsboards for each month using various filters. The issue is that by using the "created" filter to look at only Januarys issues, its excludes tickets that have rolled over from the previous month. Is there a way to look at the data monthly but also include tickets that have rolled over from the previous month?

Matthias Gaiser _K15t_ · Answer

I'm not sure if I've completely understood you, but still throwing in some ideas maybe help you further:

* If you want to see all issues which were created in the current month or are still "blocked", you could filter for that in the JQL, e.g.(created >= startOfMonth() and created <= endOfMonth()) or status = "blocked"

This assumes that "blocked" is a status field.

* I'd probably recommend more to only look at all the issues which are there, but haven't been resolved which you could do with a simple.resolution = Unresolved

This would still list all open issues from the months before - but not sure if this is what you were asking for.

Note, if you have Atlassian Intelligence activated, you could also describe in natural language which issues you'd like to see and let AI create a JQL for you.

Jonathan Davis · Answer

Thanks Matthias, thats helpful. The problem Im facing is that sometimes we have tickets that are created in January but are put into "blocked" until March.  Then when looking at Februarys data they dont appear. Appreciate this isnt the proper use of Jira/Agile but we would like to include these tickets in our data if possible. Thanks again!

Matthias Gaiser _K15t_ · Answer

Hey @Jonathan Davis

there are different possibilities for that. The main question is: Which issues do you want to see?

* All the issues which were created in January? 
-> use the created field
* All the issues which were updated in January?
-> use the updated field
* All the issues which got resolved in Januar?
-> use the resolved field

If you are more specific with your criteria, we can also help you come up with a more specific JQL query.

Cheers,
Matthias.