...
The estimate form controls help calculate the amount of work in days an issue might take. The following table provides some example examples of the results of different values:
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 median
Story points
Confidence Field
The confidence field adjusts the estimate using a log-normal distribution. Learn more about this here.
Defaults to the following fields if they exist:
Story points confidence
Confidence
Velocity
How many “estimate units” are completed by the whole team every sprint.
Sprint Length
How many days each sprint takes.
Tracks
On average, how many parallel issues of this type the team will work on at once.
...
Projects can be set up completely differently across a Jira instance. The fields that represent dates can also vary across issue type.
In order to report on dates, the tool needs to know which date fields it should use.
In order to calculate percentage completion, the tool needs to know which field holds the estimate, the team’s velocity per sprint, and how long a sprint lasts.
⁃ It also
...