Previous Month Bug Status

[Franzisca Lindner]

I am trying to create a status dashboard where one contains all the current bugs and their current status and one which contains all bugs but shows what their status was in the previous month to see any progress in the number of open/in progress bugs. Any idea how this can be achieved? 

[Valeriia_Havrylenko_SaaSJet]

Hi @Franzisca Lindner  👋

Unfortunately, there is no way you can find with native gadget, but you can achieve it with Time in Status for Jira by SaaSJet.

You can view data as a Table or Chart. And use a Pivot to customize your reports as you need. Also you can create a  Gadget and control time in status data in the Issue List or Chart View.

Moreover, you can export all necessary data as a report in XLS or CVS files and set up a teamwork schedule to exclude non-working hours or days.

Also we built new feature Sprint Performance Report, where we have all the metrics for each sprint. You can see here added, removed, completed and not completed Story points and your team Velocity in the sprint. 

       

I would be happy if you had a look at it! 

Try Time In Status for Jira + Sprint Report for free.
Hope it helps 😌

[Danut M _StonikByte_]

Hi @Franzisca Lindner,

For showing the bug statuses along the time, your best option would be a Cumulative Flow Diagram (CFD) chart. Unfortunately Jira does not have a CFD gadget, but you could try the Cumulative Flow Diagram (CFD) gadget offered by our Great Gadgets app.

All you need is to have a filter or JQL that returns all the bugs and then to configure the gadget to use it and to group the data by 4-weeks or 1-month interval.

Hope this helps.

Danut

[Gizem Gökçe _OBSS_]

Hello @Franzisca Lindner ,

I believe Timepiece - Time in Status for Jira which is developed by my team at OBSS, has a report type that will meet your need.  Our app is available for both Jira Cloud, and Data Center. 

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get metrics like Response Time, Resolution Time, Issue Age, Cycle Time, Lead Time etc. For all numeric report types, you can also calculate averages and sums of those durations grouped by the issue fields you select. 

Using your case as an example, if you create a report that groups issues(bugs) by year and month of creation, you can easily see their current status, compare months and perform trend analysis. (See screenshot below) 

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts. And the app has a REST API so you can get the reports from Jira UI or via REST. Also you can export the reports in to various formats easily. 

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process. Enjoy a 30-day free trial to experience the full range of features.

Hope it helps,

Gizem

[Jack Brickey]

Hi @Franzisca Lindner , in order to achieve this you would need to create a custom field (status last month) and populate the field using Automation. However, I really am questioning the value/reliability of the goal given a status can change any number of times. Would you want to track the previous status as entering or exiting a month?

[Franzisca Lindner]

Hi, the goal is to see how many bugs we had last month compared to this month - but also to see how many we had in each Status last month compared to this to be able to see the growth/decline of our bugs (e.g % of closed has down on previous month etc) - something like the below

[Jack Brickey]

While it doesn't provide the status breakdown, I would recommend simply using the created versus resolved so that you could trend it overtime. if you want to capture the previous month, I would recommend leveraging confluence and simply taking a snapshot each month. Again, do you need to figure out when you're gonna take that snapshot to represent the previous month. I would guess you would do it on the last day of the month.