How to list JIRA's created by a user in a time period?

[J S S S Bharath]

I have 20 users, and I want to find out the below  

1. How many JIRA's are created by an user in a period of time (a month)?
2. How many JIRA's are updated by an user in a period of time (a month)?
3. How many JIRA's are closed by an user in a period of time (a month)?

I want to see this in a confluence page. Is this possible?

[Jehan Bhathena]

Hi @J S S S Bharath ,

For the below use cases you can try the attached JQL:

1. How many JIRA's are created by an user in a period of time (a month)?
   • created >= -30d AND creator =<user UID>
2. How many JIRA's are updated by an user in a period of time (a month)?
   • Haven't tried this yet, not sure if JQL out of the box supports this yet
3. How many JIRA's are closed by an user in a period of time (a month)?
   • created >= -30d AND status changed BY <user UID>

In theory you can also use the "created in last 30 days" jql and pair it with the Pie chart dashboard to see how many creators are there in the one month:

Let me know if this helps.

[MobilityStream]

Hi @J S S S Bharath ,

This can easily be accomplished by exporting Jira issues and changelog data to a spreadsheet and using Pivot tables. In this case I’m using our Google Sheets Integration add-on. If you don’t feel like setting up a GS integration, the exact same functionality will become available in our Excel Integration add-on (nothing to set up there, simply download the xlsx file and do the same thing in Excel) over the next few days.

Here are the steps:

1. Export Jira issues and changelogs to a spreadsheet

• Include Created, Reported, issue Key fields at a minimum
• Include Changelogs

2. Create a Pivot table for Created by month/reporter (based on Jira issue Data tab)

• Rows: Created field
• Columns: Reporter
• Values: Issue Key
• Create data pivot group: month

3. Create a Pivot table for updated (based on Changelog tab)

• Rows: Created field
• Columns: User
• Values: Issue key

4. Create a Pivot table for closed by month/reporter (based on Changelog tab)

• Rows: User field, To field
• Values: Issue Key
• Filter: by value: Done (or whatever your closed status is)

If you need help with this, we are happy to help. Send us an email to support@mobilitystream.com

Kind regards,

The Mobility Team

[J S S S Bharath]

Hello,

Is there a solution without using any addons?

Warm Regards

Bharath

[Aron Gombas _Midori_]

It could certainly be solved by a custom-developed app or maybe one of the reporting apps that offer Confluence integration (EazyBI does).

An alternative is that the Better Excel Exporter can create you a pivot table using the built-in created-vs-resolved.xlsx report template.

This configuration shows you a per-project per-year-and-month breakdown of the data, but you could similarly add new fields to this:

(Disck. the Excel exporter is a paid app that is supported by our team. Free for 10 users.)

[Tuncay Senturk]

Hi @J S S S Bharath 

Using the default features of Jira, you can only address the first requirement. Utilizing the createdDate and reporter/creator fields in JQL searches allow you to find issues created within a specific timeframe by a particular user:

createdDate >= startOfMonth() AND createdDate <= endOfMonth() AND author = "username"

Similarly, the updated field can be used to filter issues that have been updated during a specified period, but unfortunately, you cannot filter by the users who performed the updates.

For the third requirement, you can create a custom field and update it during the "Close Issue" transition. However, this modification will only apply to issues closed after altering your workflow; already closed issues won't be affected.

If you have the flexibility to leverage apps from the Marketplace, I recommend considering the Enhancer Plugin for Jira. This plugin enables the creation of fields similar to those mentioned above using Enhancer's Date fields. After reindexing Jira, you can filter issues using these fields, impacting even already updated issues and including them in search results.

These fields can be seamlessly integrated into Confluence, behaving like any other custom fields. As one of the contributors to this app, I assure you that our team is ready to assist if you encounter any issues. Feel free to reach out for support.