Is there a way in eazybi we can find the number of days it took from defect in Open status to Ready to Test( available for QA to TEST). Basically trying to find the ageing of defects since its logged until its available to TEST and see the developers productivity.
f you would be interested in a ready made solution, you may want to try out our plugin,
The add-on provides the time spent in each status for the entire lifecycle of the issue. You can also extract the transitions history of the issue. Along with various Issue stats reports, you get additional features like Epic Hierarchy & Links Hierarchy to track the project's progress. The main features are as below
Hi @Clicker ,
As an alternative, you can try Status Time app developed by our team. It provides reports on how much time passed in each status as well as status entry dates and status transition count.
Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project). And all these are available as gadgets on the dashboard too.
I am afraid there is no way to do this out-of-the-box and but there are some solutions worth mentioning here (surely not part of an eazyBI solution as presented here):
You can use the built-in Control Chart (that is available as part of Kanban Board reports) about this but it is not very good with reopens. It will show you durations but it won't show individual issues. It is more aimed towards seeing the big picture. Plus, you can't get its raw data.
There are the Average Age Report or Resolution Time Reports. Both are available under project reports or as dashboard gadgets. Unfortunately, both reports also are very high level. They are not very flexible, just show daily average data and don't show individual issue data. Average Age Report excludes resolved issues and Resolution Time report excludes non-resolved issues so resolving an issue excludes that issue from one report and adds it to the other. This causes unexpectedly rapid changes in those reports.
The only remaining option (without using a marketplace app) would be to use the cloud REST API to collect the data yourself and do some custom development to build the reports you need.
In case you are OK with using a marketplace app, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud, and Data Center.
Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Resolution Time, Cycle Time, or Lead Time.
You can calculate averages and sums of those durations grouped by the issue fields you select. (For example, see the total InProgress time per Epic or average Resolution Time per issue type).
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.
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.
Using Time in Status you can:
If you need to calculate time from Open status to Ready to Test, try Time in Status for Jira Cloud developed by my team. It allows generating reports with cycle and lead time. You can group any statuses you need here.
5 steps to configure:
1. Select Time in the Status report and required project
2. Open columns manager
3. Choose Add New Group in Status Groups menu
4. Add a name and statuses you need, and save.
5. Save the column to display it.
As a result, you'll get an additional column with time calculated for statuses you've chosen depending on the workflow you use.
Hope it helps. Let me know if you have any questions.
eazyBI by default imports lead time (Average resolution days - since issue creation till resolution) and closing days (Average closing days - since issue creation till issue closing).
We have an option to analyze any other cycles as well, they could be customized as needed. Here is an example report for cycle time calculations based on different rules. You can export the report and import it into your account or copy the needed formula explicilty.
It seems you can use a measure Average days in cycle. Please define a custom cycle by listing statuses in calculated member Custom cycles in dimension Transition status. See examples for Custom cycle in Transition status in our demo account.
Daina / email@example.com
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events