I want to show based on month end date, how many tickets had certain value in the field e.g. color borwn. Ho many tickets had value brown at the end of month and so I can see trend how the values have been change month to month
Hi @Martin Vali
Short answer: that is not possible with built-in dashboard gadgets / reporting, and marketplace apps would be needed instead.
The changelog / history for work items usually contains the information for reporting like you asked. However, accessing that changelog is quite difficult with built-in Jira features. And only a few fields have access to the changelog using JQL.
There are several marketplace apps which can access the changelog to report on field values over time. Please consider your specific needs, and then review apps to find / try one which helps: https://marketplace.atlassian.com/
Kind regards,
Bill
Hi @Martin Vali
You can use Jira Rest Api's to pull this information and build your own custom solution.
However if you need detailed reporting to track changes for multiple issues, you may want to have a look at a mktplace app for the same.
We have built an app to extract changelog data in a simple and easy to use interface. The data can be exported to a CSV file as well.
It provides complete details of who added comments, what was changed and when.
Do give it a try.
Disclaimer : I am part of the app dev team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Martin Vali
Native Jira dashboards are excellent for real-time reporting, but they generally reflect the current state of your issues. Natively, Jira does not easily allow you to take historical snapshots (like checking what a custom field value was at the exact end of last month) to build trend reports out-of-the-box.
If you are open to using a third-party app, you can easily reconstruct your backlog and track these month-over-month field trends using Historian - History Explorer for Jira.
Here is how you can use its features to get exactly what you need:
Historic Query: Historian features a dedicated Historic Query report that allows you to view the results of a JQL search exactly as they appeared at a specific point in time in the past. Because it relies on your existing Jira issue history, you don't need to wait to start collecting data, even if you install the app today, you can instantly run retrospective reports for any past month.
Results As Of: You can use your standard JQL to filter your tickets, and then use the "Show me the results as of" date picker to select the exact end date of the month (e.g., June 31st). The report will dynamically show you the exact field values—like your color field—as they appeared on that specific date.
Export for Trend Analysis: Once you generate your month-end snapshots, you can instantly export the data to an Excel (XLSX) or CSV file. This makes it incredibly easy to track your month-to-month trends and build charts for your stakeholders.
You can find Historian - History Explorer for Jira on the Atlassian Marketplace.
Full disclosure: I am part of the OBSS team, the creators of Historian. Hope this helps you get the exact trend visibility you need!
Best,
Birkan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Martin Vali,
Unfortunately, Jira does not provide this type of dashboard gadget out of the box.
The best approach is to look for an app on the Atlassian Marketplace that offers this functionality.
If you'd like to try a plugin, I recommend our Great Gadgets app. It includes several dashboard gadgets that can easily address this requirement.
Cumulative Flow Diagram gadget - lets you display the historical data for the issues in a filter split by a selected field. In this example I used Status field, but it works the same for your Color field.
You can use this to see the evolution of all the Brown issues over time. You can group data by calendar months.
WIP Run Chart gadget - lets you display the historical data for the active (not-resolved) issues in a filter split by a selected field. In this example I used Status field, but it works the same for your Color field.
You can use this to see the evolution of all the not-resolved Brown issues over time.
All you have to do is to configure the gadget with a filter/JQL that return the issues, set the time rage, and split the data by your Color field.
The gadgets can be configured to display only Brown series. You can group data by calendar months. Also you can customize the color of the series, to match your field values (for example, display the Brown series in brown color)
Danut.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.