...
How many days each sprint takes. This is typically a multiple of 5. This For example, use 5 for a one-week sprint.
Sprint length defaults to 10 for a two-week sprint.
Tracks
...
...
The tracks field specifies the average parallel tracks of work the team works on at once. For example, if the team works on about 4 stories at once, you should set the tracks to 4 for stories. Your team might have different values for epics and other issue types.
Tracks is used to calculate the number of days of work the issue might take. Consider the following values for an issue:
Story Points:
20Velocity:
40Tracks:
1Sprint Length:
10
StatusReports will calculate the issue will take 5 days. It assumes the entire team is working on that issue. If instead, your team typically works on two of these issues at once (tracks = 2), then StatusReports will calculate the issue takes 10 days.
Spread Effort
...
The Spread Effort toggle spreads the estimated effort across the start and end date timeframe. This
...
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
...