Teams
Teams are named groups of Jira users that can be reused across the Capacity Planner, Time Tracking Reports, and Portfolio module for group-level filtering, grouping, and reporting.
Opening Team Management
Team Management is not a standalone module - it's a section available from inside both Capacity Planner & Insights and Time-Tracking & Reporting, with Teams, Programs, and Capacity tabs.
Creating a Team
-
Click Create Team
-
Fill in the team form:
Field Required Description Team Name Yes Display name (e.g., "Platform Team", "QA Squad") Description No Brief description of the team's role or scope Color No Colour tag for visual identification in views Members Yes Add individual users by search -
Click Save
How Members Are Added
Members are added individually by searching for Jira users - there is no Jira Group auto-sync option. If your team's membership previously tracked a Jira group automatically, that sync no longer exists; membership now needs to be kept current manually inside the app.
Using Teams Across Modules
| Module | How Teams Are Used |
|---|---|
| Capacity Planner | Group By → Team - shows rolled-up capacity per team |
| Reports | Filter by Team - restricts the report to selected team members |
| Time Tracking Reports | Filter or Group By → Team |
| Portfolio Management | Assign portfolio scope filtered to team members |
Managing Teams
| Action | How |
|---|---|
| Edit team | Teams list → Edit (pencil) icon → modify → Save |
| Add member | Edit team → Members field → search and add user |
| Remove member | Edit team → Members list → click × next to user |
| Delete team | Teams list → Delete (trash) icon → Confirm |
Deleting a team does not delete users or their worklogs. It only removes the team grouping.
Tips
- Create teams to mirror your actual squad structure - this makes capacity and time tracking reports immediately meaningful to team leads
- Since membership is manual, revisit team rosters periodically rather than assuming they track Jira group changes
- A user can belong to multiple teams (e.g., a shared QA engineer on both the Platform and Frontend teams)