Forums

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

A way to find out number of issues being updated during certain period in time

Joanna Bajda
Contributor
July 6, 2020

Hi,

 

I'm looking for a way to get information from JIRA Cloud:

1. How many tickets have been updated (manually by users or by pull request) in last week, two weeks, month etc.

2. How many users works on issues - there's no worklogs done on issues at all, so this probably can be calculated based on first question results.

I'll be grateful of any suggestion, as I stuck with this. Is there any add on to help with this? 

 

Joanna

3 answers

1 accepted

2 votes
Answer accepted
Mykenna Cepek
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.
July 6, 2020

You can experiment with the Issue Search in Jira to try out various queries. Click on "Issues" in the left navbar of Jira (from the Backlog or Board view). Near the top, click on "Advanced search", and now you can explore the data with JQL (Java Query Language).

This JQL will show you the issues that have been updated in the last week in a project:

project = "ABBR" AND updated > -7d

The "-7d" means seven days, but in the past (due to the minus sign). "-1m" would be one month in the past. The "updated" field in Jira stores the date when the issue was last modified.

For your second item, I'm less sure what to suggest (I'm not exactly sure what you want). You could sort the above results by the user who is assigned to the issue, and just count the number of different users manually.

project = "ABBR" AND updated > -7d ORDER BY assignee

Assuming your version control system is linked to Jira, you could also explore the "developer status" features of JQL, which are documented more here:

https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-developer-status/

Good luck, and best wishes! 

Joanna Bajda
Contributor
July 6, 2020

Hi Makenna,

Thanks for the answer, I was looking for something that will give me (my customer) clear and easy answer as a number of issues worked on - so I can create a filter based on query you advised, but it will not count pull requests.  I was hoping for some add on or dashboard gadget that shows data when needed.

JeyRoik
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 23, 2022

Mykenna, is there any way to find issues that have any updates on the given period?

If issue was updated 7d before and then was updated today, then it wouldn't be in a result by your query. Is there any way to find such kind of issues?

Like # people like this
2 votes
Mariana_Pryshliak_SaaSJet
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.
July 7, 2020

Hello @Joanna Bajda 

You can try Issue History to solve your issue.

Choose the period you need and get all the history changelog data. It will include the list of issues that have been updated, info about users who have been working on issues, and which changes have been made to these issues.

IH.png

To analyze the number of tasks that have been changed and the number of users that have made these changes, you can export the data as XLSX or CSV files. 

That is very comfy because you have all the data in a few clicks and in one place.

If you have any additional questions, don't hesitate to contact me.

Best regards, Mariana

2 votes
Gökçe Gürsel {Appfire}
Atlassian Partner
July 7, 2020

Hi Joanna,

Given that there are no worklogs present in the issues, I recommend using Time to SLA to see which users are working on which issues. You can also get summary reports and detailed reports to see whether your users are on top of their workloads. Also, since there are no worklogs entered by the users, you can just define your SLA and regenerate the SLAs to have historical data on issues.

Brow report summary.pngBrow detailed report.png

Time to SLA offers an easy to use solution for your use case. Let me know if you have any questions.

Best,

Gökçe

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events