Tasks breakdown

The tasks breakdown shows an overview of all the tasks in this sprint. Use this to see where each task started and ended, and what was the actual time each task was "in progress".

You can sort and filter each column to easily navigate through your task list.

Each issue shows the following data:

Planned/unplanned

Indicates whether the issue was originally part of the sprint or not. Unplanned will indicate an issue was added to the iteration after it has started including the grace period.

Story points/estimated time/sub-tasks

In case the sprint monitoring is configured to be calculated by story points of time estimate, it will show the relevant SP amount or time estimate.
​

In case this field is configured as “none” (no estimates):

• If a story or a task has sub-tasks it will show the number of subtasks under the relevant story/task.
• If a story or a task doesn't have sub-tasks, it will show “1.”

Actual cycle time

Shows the time an issue has spent in the “in-progress” cycle, usually from status “selected for development” to “done” (statuses may change according to the company workflow).

State Progress Bar

Shows a complete breakdown of each task's cycle time. Use this to get a clear picture of your actual cycle time and understand each stage of your development cycle.
​

Status

• Start status - the status of the issue at the time the sprint started.
• In case the issue was created in the middle of the sprint, the start status will show “created.”
• In case an existing issue was added in the middle of the sprint, the start status will show the status of the issue at the time the sprint started.
• End status - the status of the issue at the time the sprint ended.

Sprint task views is a quick and simple way to look at the issues in the sprint, divided into groups which can help the team instantly understand what happened during the sprint:

• Planned and completed - all planned issues that were completed during the sprint.
• Planned and not completed - all planned issues which were not completed during the iteration, including issues that were removed during the sprint.
• Added mid-sprint - all unplanned issues.
• Carryover and not completed - issues that were carried over from the previous sprint and not completed during the current sprint.

💡Are you using Kanban boards or Jira server? Contact us over chat for more info!