...
Each issue is mapped to a team value. The team value determines how values from that issue will be read. If the issue does not have a team value, then the issue’s project key will be used.
Date Form Controls
The following controls how Status Reports know when an issue starts and ends.
Start Date Field
...
...
Set the Start date field to the Jira field that represents when the issue is expected to start.
Defaults to:
Start date
End Date Field
...
...
Set the End date field to the Jira field that represents when the issue is expected to end.
...
Estimate | Confidence | Adjusted Estimate | Velocity | Sprint Length | Tracks | Points Per Track per Day | Days |
|---|---|---|---|---|---|---|---|
10 | 100% | 10 | 20 | 10 | 1 | 2 | 5 |
10 | 100% | 10 | 20 | 10 | 2 | 1 | 10 |
10 | 50% | 18 | 20 | 10 | 1 | 2 | 9 |
Estimate Field
...
The estimate field is a number field that provides some sort of estimate of the amount of work on the issue. This will be converted to days of work using the Confidence, Sprint Length, Velocity per Sprint, and Tracks fields.
...
Story points confidenceConfidence
If you are not using confidence, you can set this field to: “Don’t use confidence” as shown below:
...
Velocity
How many “estimate units” are completed by the whole team every sprint. This number depends on how your team is estimating work. The following give some examples of what the velocity would be in different estimation approaches:
Approach Name | Description | Example Estimate Values | Example Velocity |
|---|---|---|---|
Story Points | How many story points would you estimate for this work, based on its complexity and effort? | A team might estimate an issue as | For the past 5 sprints, the team has averaged completing 23 points a sprint. The velocity would be |
Combined Days | How many combined total days of work will the issue take across all team members? | The work will require 2 days of designer time, 5 days of developer time, and 1 day of QA time, for a total of | There are 5 team members in total, and each sprint lasts 10 days. Each sprint completes |
Team Days | How many days of work the issue will take if the entire team is working on the issue and is able to be fully utilized? | The work will take | If a sprint lasts 15 days, there are 15 “team work days” each sprint. The velocity would be |
Half Team Days | How many days of work the issue will take if half the team is working on the issue? | The work will take | If a sprint lasts 15 days, there are 30 “half-team work days” each sprint. The velocity would be |
Sprint Length
How many days each sprint takes.
...