User Guide
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 Teams Management
Global sidebar → Teams Management → Teams
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 Source Yes Manual or Jira Group Members Yes Add individual users or select a Jira Group -
Click Save
Team Sources
Manual Source
- You manually add and remove members
- Members remain fixed until you edit the team
- Best for stable, long-term teams or cross-functional groups not matching a Jira group
Jira Group Source
- Members are automatically synced from a Jira Group
- Changes made to the Jira Group (add/remove member) reflect in the team automatically
- Best when team membership is already managed in Jira
Using Teams Across Modules
| Module | How Teams Are Used |
|---|---|
| Capacity Planner | Group By → Team - shows rolled-up capacity per team |
| Capacity Report | Filter by Team - restricts the report to selected team members |
| Time Tracking Report | Filter or Group By → Team |
| Portfolio (PPM) | 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
- Use Jira Group as the source if you already manage team membership in Jira - avoid duplicating maintenance effort
- A user can belong to multiple teams (e.g., a shared QA engineer on both the Platform and Frontend teams)