QA availability

About this report

The QA Availability report captures the total estimated QA task hours per sprint versus the total QA task hours actually logged per sprint. In other words, how did the actual time spent on the tasks compare to what you estimated? This report provides this comparison over the previous 3,5, or 10 sprints using a bar graph. The X axis of the graph shows the estimated and actual categories being compared, and the Y axis represents the total task hours value.

This report can be used as a coaching tool by Scrum Masters, team leaders, and product owners to assess the accuracy of QA task estimates, and also to track actual QA time logged per sprint. It is beneficial to review the report with team members during pre- and post-PI meetings, general team meetings, and during sprint review meetings. This report is generated by selecting a specific team tied to a specific program.


  1. Select the Reports icon from the left Navigation menu.
  2. Start typing the report's name in the Search box. 
  3. Once found, select the report.

Note: You can also use the categories on the left to search for the needed reports.


  1. PI must exist in the system and be tied to a program. 
  2. Sprints must be created and tied to a PI. 
  3. Teams must be created and tied to a program. 
  4. Stories must be created and tied to a sprint. 
  5. Tasks must be created and tied to stories.
  6. QA task hours must be estimated and logged. 

How are report values calculated? 

  • Estimated QA task hours are pulled from all QA tasks assigned to stories in the specified sprint for the selected team; the QA task hour estimates are entered via the Task Grid/New Task panel.
  • Actual QA task hours are pulled from logged QA task hours for stories in the specified sprint belonging to the selected team; actual logged QA hours are entered by clicking the Clock icon for any tasks listed for a story; this can also be performed using the same Clock icon in the Team Room, List view.


How to interpret this report

Ideally, estimated task hours should be fairly equal to actual task hours. Pay particular attention to the variance in height of the two bars in the graph--variance can also be calculated by <Estimate hours> - <Actual hours>. When actual hours are less than the estimate hours, variance is positive and means there are additional task hours remaining for work in the sprint. When actual hours are greater than estimated hours, variance is negative and means extra time was needed to complete the tasks. Over multiple sprints, repeated variance (either positive negative, or both) shows the need for the team to work on creating more accurate estimates.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.