An alternative answer is to consider what statistic is required.
The reply by @Gabrielle Bautista [ACP-JA] tells you how many issues were created in a month and are now resolved it does not tell you how many are still open nor how many were resolved in the specific month.
I believe a more meaningful measure is to know the difference between created/resolved in a month. This takes in to account that at the start of the month you will have some unresolved issues carried over from previous months and at the end of the month some will be carried over to the next month.
To achieve this I would look at capturing two sets of statistics and then perform a simple calculation.
Project = PROJECTPARK and Created >= 2015-11-1 and created <= 2015-11-30
Project = PROJECTPARK and ResolutionDate >= 2015-11-1 and ResolutionDate <= 2015-11-30
You could look at extending this through the use of a calculated field to determine the average resolution date for all issues.
After playing around a bit, I was able to get what i needed by using this JQL
project in (PROJECTPARK) AND issuetype in standardIssueTypes() AND status was in (Open, "In Progress", Blocked) DURING ("2015-10-01","2015-10-31") AND status was not in ("Resolved", "Closed") DURING ("2015-10-01","2015-10-31")
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs