User information
 Loading ...
Show article in Knowledge Base

 The Sprint page Export knowledge base Export     SubscribeSubscribe      Show article info

The sprint page is where you get an overview of sprint data for the project.


 Note: We use the term 'sprint', but many call it by other names - release, iteration, timebox, milestone, version, phase among others.

The important thing is that it is a number of issues grouped by a common deadline.


Sub-tabs under sprint tab:

  • Sprints: the sub-tab for the sprints info page.
  • Burn-down: Shows the burn-down graph for the version. Also possibly edit of remaining time
  • Build history: Create and show builds for sprints
  • Release notes: View release notes for the sprint (completed issues)
  • Edit release notes: Edit or create release notes for a sprint


The sprint page has three parts:


1. Open versions timeline: This is a graph showing a very simple gantt chart for the sprints. This graph can easily be collapsed by clicking on '[Hide]'.


Below are three functions:

  • Create new sprint: Goes to the Create/edit sprint dialogue where you can create a new sprint. 
  • Show closed sprint: By default you only see active sprint. Check this to see the old inactive sprints as well.
  • Show sprint details: Uncheck this to only see the first line of sprint info (number, desc, start/stop date and progress bar)

When Show sprint details is choosen the rest of the table shows the detailed information for the sprints  of  the project, one per row:


2. Sprint info data: This section contains the aggregated information for the sprint.

  • First row: Basic sprint data.
  • Order: The order number, used for ordering sprints among themselves. Lowest number comes first: 0, 1, 2, 3 and so on.. 
  • Closed: Sprint is closed
  • Sprint number: Can be a straight number, or a interpunctuated one, like '3.2.1'. Click on the sprint number to go to the 'Edit version' page where you can change version specifics, and also see the issues in the sprint.
  • Description: A sentence here can be a good reminder of what the goal is for this sprint.
  • Start date: Date when work on the sprint started.
  • Release date: Date for the deadline.
  • Progress bar: Shows how far along work is on the sprint, at a glance. Also shows the number of opened and closed issues on the sprint.
  • Times/Cost summary from issues: This section shows a time/money summary
  • Estimated time: A sum of estimated time on the sprint
  • Actual time: A sum of the actual time fields on the sprint issues.
  • Remaining time: A sum of the remaining time on the sprint.
  • Estimated billing amount: When using costs on the project, you can see how much you can be billing for this version, based on the estimated time
  • Estimated cost amount: When using costs on the project, you can see how much this version is going to cost, based on the estimated time. (Cost = internal cost)
  • Time/Cost summary from issue worklogs: This section is based on time reported on worklogs on version issues.
  • Total time: The total reported time
  • Billable time: Sum of the time marked as billable.
  • Billing amount: The total money billable. Based on project defined costs, and the billable time.
  • Cost time: Sum of time marked as costable (internal cost).
  • Cost amount: The total internal money cost. Based on project defined costs, and the cost time.


3. Resource availability for version:
Click on the number in the Sprint number column. This section shows how much work time is available to the sprint, and who works on it.


On the left hand side summaries of Time/Cost, Issues and Hours can be found.

In the the center view you can find:  

  • First, a sum of the total available time, in hours. 

  • Below that is Manage resource availability for sprint which is an expandable section where you can see the table of users assigned to the project version, and how much they can work on the version each week.    - One row per user.
    - The column headers in the table are week numbers. Use the green arrows to shift the viewed time frame forward or backward. By default the first column is the current week.
    - Each cell represent how many hours that user can work on this project version during the week in question. 

To edit, just click on the cell and type the new value. Be sure to click on the 'Save' button to update the table.


  • Furthest down are the charts: Progress, Time and budget and Hours per user



User comments
 Loading ...