I am not sure if anyone else facing the same issue but it is crucial for us to generate reports and track metrics such as Lead time, Cycle time and Throughput on ideas we populate on JPD.
We need to measure how long it takes to take action and eventually deliver work via JPD.
Keen to understand if anyone else facing the same challenge if so how to get around the limitations of JPD.
Thank you.
Ciao!
As you for sure know, Issues of Jira Product Discovery can be seen also from Jira with appropriate queries.
If you have a way to capture the above metrics on Jira, you can get them from Jira Product Discovery as well.
FYI we are starting using ActionableAgile collecting JPD key info...
Cheers,
Simone
Hello @Aidin Mahmoodi {ServiceRocket} 👋
If you're interested in an add-on, consider trying Time in Status. It allows you to create Cycle or Lead time reports, display them on your board, and export them for further analysis.
Just simply:
You can also check out a short use case on how to get Cycle and Lead time for Jira issues, as well as an article about Reporting on Jira Product Discovery
Add-on has a 30-day free trial version and free up to 10 users, and developed by my SaaSJet team
Hope it helps 😌
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.
Hello @Aidin Mahmoodi {ServiceRocket}
Ideas are also represented with Jira issues underneath so anything that works for Jira issues should work for ideas too.
Our team at OBSS built Time in Status for this. It is available for Jira Server, Cloud, and Data Center.
Time in Status mainly allows you to see how much time each issue spent on each status. You can do the same for ideas.
You can combine the time for multiple statuses to get metrics like Idea Age, Lead Time, Cycle Time, etc.
For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per component or average cycle time per product, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.
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.
https://marketplace.atlassian.com/apps/1211756/
EmreT
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.