How to migrate from Agile Reports for Jira?

Overview

After careful consideration, we have decided to retire Agile Reports for Jira as part of our ongoing product lifecycle management process. While this app will be retired, we recommend existing customers use Reports and Timesheets for Jira for many of the same reporting features. To help make this transition easier, we’ve emailed a notice and discount code to all current customers to purchase Reports and Timesheets for Jira.

You can continue using your installed license, and we will continue supporting customers with active licenses, but we will no longer release updates through the Atlassian Marketplace. We will archive the app on December 15, 2022, and your license will no longer be renewable 90 days before this date.

We sincerely appreciate your understanding, and we hope the impact on your organization and customers will be minimal. Please don't hesitate to contact our support team if you have any questions. 

Why Reports and Timesheets for Jira?

We recommend using Reports and Timesheets for Jira for many of the same reporting features — available on the server, Data Center, and cloud. This solution offers an all-in-one reporting and time tracking app that simplifies sprint tracking, including key reports like sprint burndown, sprint velocity, sprint performance, and more.

Feature Parity

 

Agile Reports for Jira

Reports and Timesheets for Jira

 

Agile Reports for Jira

Reports and Timesheets for Jira

Burnup / burndown report

The Burnup / burndown report shows information on how the team is performing towards the specific goal. 

View more information in the app documentation.

Sprint Burndown - This report shows the burn down data of current and completed sprints. It’s useful to understand how a sprint progressed over time, scope additions, and the rate of completion.

View more information in the app documentation.

Committed vs Completed report

The Committed vs Completed report displays the following information:

  • Commitment for each sprint measured in man-days or story points

  • Actual work delivered measured in the same metrics

  • Estimation Error – a red line indicating the estimation error as a percentage for each sprint. This line helps you identify the accuracy of how your team is providing estimations. If the estimation error decreases, it means that the team is getting better and more precise in measuring the assigned tasks, thus you are on the right track.

View more information in the app documentation.

Sprint Velocity - This report shows the committed vs. completed issues of a selected sprints. It’s helpful to use to estimate future velocity and plan commitment for new sprints.

View more information in the app documentation.

Committed vs Completed report

Committed vs Completed report shows the estimate accuracy for your team from sprint to sprint and helps answer the following questions:

  • are we overcommitting?

  • are we getting more accurate in our estimates?

  • what is the average team velocity (so that I can plan the next sprints better)?

View more information in the app documentation.

Sprint Performance - This reports shows a detailed report of committed issues, net scope change for committed issues, completed issues, remaining effort, scope additions, and scope removal for a range of sprints. It’s very useful to understand a full view of a sprint’s planning based on the trend of net scope change over sprints and it’s effect on velocity.

View more information in the app documentation.