...

• Capacity (hours) - Show planned work calculations based on hours estimations (if hours estimations in use).

• Capacity (story points) - Show planned work calculations based on story points estimations (if story points estimations in use).

  

• Tracking - Amount of planned work compared to the logged work by the team-sprint assigned resources (Planned Work vs. Actual Work). The calculation base used when in Tracking mode depends on the estimation method set for the Board (see above).

Sprint Planning

...

Planned work capacity is calculated based on the issues Time Remaining field values ( not Original Estimate value), giving the sprint planner a truer view of the actual work effort that is planned. Once a sprint starts, planned work values are locked. Any updates to the sprint's tasks Time Remaining field values (such as with log work), do not affect Planned Work values recorded when the sprint started.
Tracking actual work is calculated based on the work logged as completed in the sprint by a team member assigned to it, so for this to be accurate it is crucial that team members update their progress through the use of 'log work'.

...

• Tasks - calculate only values of issues of types such as tasks, bugs and other issue types in that same level.

• Tasks + Sub-tasks - calculate all the above elements and their sub-tasks (the original estimation given in the sub-tasks will be addressed and populated).

• Sub-tasks - calculate only sub-tasks (the original estimation given in the sub-tasks will be addressed and populated).

• Smart Calculation - Tasks + Sub-tasks, however, if for sub-tasks having original estimate, parent task values are not calculated.

Sprint Tracking

The Tracking mode is available for the current active sprint (it is not relevant for future sprints; for past sprint you can observe the actual achievements in the app reports). Tracking allows you to observe how the progress of current active sprint compared to the work planned for it, before it was started. Therefore, the tracking mode freezes the estimated work just as the print was launched as the reference for the sprint planning goal. The app ignores, therefore, “estimation” changes that were made in the active sprint after it was launched. This ensure honest progress report evaluation compared to the original planning goal.

...