A team's Preferences section, below its data source, sets defaults for new work and each member's share of the team's capacity.
Defaults for new work
- Default Issue Type for New Tickets — the task type new tickets get automatically.
- Default Sub-task Type for New Tickets — Jira and GitHub teams only.
Capacity and lead time
- Max points per member — a slider over 1, 2, 3, 5, 8, 13 points, the ceiling used for a member's single-sprint capacity.
- Lead Time for Changes — a slider from 2 hours to 30 days, showing a DORA category pill: ELITE (under 24 hours), HIGH (under 7 days), MEDIUM (under 30 days), or LOW (30 days or more).
Member allocation
Under Members, use Add member to bring someone onto the team, then set their Contribution — 0, 20, 40, 60, 80, or 100% — to reflect how much of their capacity this team gets. Remove a member with the trash icon next to their row.
What to do about it
The bottom of the page shows how many boards the team is used in — a team can't be deleted while it's used in any board; the Delete Team button in the Danger Zone stays disabled until you remove it from all of them. See Capacity and Availability for how these per-team settings roll up into a sprint's overall capacity figure.