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

Is there a SIMPLE way to create a report that shows the number of tickets created per month for a specified time period?

Rob Horan

Using relative time (last x days/months/millenia/etc) is not helpful. I have been asked to generate a report in bar graph form (which I assume I will need to use a separate tool for once I have the numbers) of tickets created per month, by type. I can't find any way to do this in Jira.

Before throwing Script Runner out there please understand I am not a programmer.

By the way, for any of you doing date based searches, you may want to look at this:

https://answers.atlassian.com/questions/30949194

Accepted answers

All comments

Scott Dudley [Inactive]

If your budget does not limit you to only free options, and if you have a behind-the-firewall installation, the Arsenale Dataplane add-on can easily tackle this task using the "Issues Created by Date" report.

In this case, you would be able to get both the bar graph and the numbers without using any external tools (and your data can also be displayed in a dashboard gadget and/or exported to PDF/Excel/CSV).

Bryan McMillan_mmet0u

Robert,

Yes there indeed is. You can use the following JQL key words of:

currentLogin()
endOfDay()
endOfMonth()
endOfWeek()
endOfYear()
lastLogin()
now()
startOfDay()
startOfMonth()
startOfWeek()
startOfYear()

In a fashion similar to this using JQL from within the Advanced (vice Basic) view under Issues --> Search for Issues:

Project = MyProject AND resolutiondate > startOfMonth() ORDER BY updated

Where MyProject is the name of one of your specific projects in Jira. You can also leave that off if you wish to pull that same information from all projects you have access to in Jira.

Hope this helps,

Bryan

Bryan McMillan_mmet0u

Robert,

My bad. If you want to do created during the month then this will do:

project = MyProject AND createdDate > startOfMonth()

Regards,

Bryan

Rob Horan

Wow. Thank you but WOW. Not free is one thing, but that's... a lot

Rob Horan

I'll give this a try, thanks!

unknown

Where will that report be? If it's in excel, exporting the JIRA issues (in JQL) then creating the bar graph in excel per se will be the simplest way to go. This is what I am doing with my other projects.

JQL: Project = ABC and created >= 2015-8-1 and created <= 2015-8-31
Export Issues into Excel (Current Fields) and leave the fields that you need
Create the Bar graph

Scott Dudley [Inactive]

I would agree that buying a paid add-on is probably not a cost-effective option if this is a one-time task and you don't need any additional reports from JIRA. (Then again, it comes with a 30-day free trial, so this may in fact be both the fastest and cheapest option if you only need to do it once!) On the other hand, if your boss wants you to produce this type of data every week, automation could prove itself valuable in the long term. :-)

Rob Horan

The only problem is that only works on a month at a time. I need to span a year, maybe two.

Rob Horan

I assume I will use Excel. To be honest I'm figuring it out as I go along

Bryan McMillan_mmet0u

This gets the current YTD

project = MyProject AND createdDate > startOfYear()

For all of 2014 YTD:

project = MyProject AND createdDate > 2014

Regards,

Bryan

unknown

Project = ABC and created >= 2015-1-1 and created <= 2015-12-31

Rob Horan

Want to know something tragic? That JQL will not work. It will omit all tickets on 12/31/2015? Why? Because, as Atlassian pointed out to me "dates in JQL are calculated as data/time values and, when you don't inform a time value, JIRA considers time as 00:00." How did this come about? I submitted the following: So, lets say you want to find all the tickets created in september. You go to the calendar and you enter dates between sept 1 and sept 30th, right? Or use the JQL created >= 2015-09-01 AND created <= 2015-09-30 Surprise! Issues created on the 30th do NOT appear in the search results. This is a SERIOUS problem for me, as I need to run monthly reports, and since Jira offers no other month based search options I rely on this. I got back: This happens because dates in JQL are calculated as data/time values and, when you don't inform a time value, JIRA considers time as 00:00 So you can either write your query as {{created >= 2015-09-01 AND created <= 2015-10-01}} or {{created >= 2015-09-01 AND created <= "2015-09-30 23:59"}} to get also the issues created in 30th. Notice that you can also write a query like {{createdDate >= startOfMonth() AND createdDate <= endOfMonth()}} and save as a filter to give easy access to all the issues created in the current month. Another query that could be useful in your case to safe as a filter would be {{createdDate >= startOfMonth(-1) AND createdDate <= endOfMonth(-1)}} which shows all issues created in the last month.

Rob Horan

I just noticed the start of year and end of year key words. Look, it takes me a while sometime. There just isn't enough coffee on some days.... All kidding aside, thank you

Midori

For non-programmers (and programmers, too), the Better Excel Plugin can generate this in a form of pivot table and the corresponding pivot chart.

The created-vs-resolved-reported.xlsx template creates something that you can easily customize, grouping creations/resolutions by month and allowing grouping those by issue type, assignee, creator, project or whatever dimension you need:

created-over-month.png

Mohammad_zulfikar

Hi scott, thank you for your info, it's very interesting to know about Arsenale Dataplaner because I wanted to make a report based on an issue type on JIRA but it's confusing how to do that. And what have you said it's a good idea, I've tried to dig it but have some difficulty to apply on my JIRA, how do I add the arsenale dataplaner into my JIRA?

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration

report