Teams & Views

Teams let you partition work within an organization so each group sees only what is relevant to them. Combined with custom views, teams can tailor their workspace without affecting anyone else.

Anatomy of a team

Field	Type	Notes
name	string	Display name — “Backend”, “Mobile”, “Platform”
identifier	string	Short prefix used in issue numbers (e.g. BACK → BACK-42); should be 2–6 uppercase chars
description	nullable
iconUrl	nullable	UI affordance for the sidebar
members[]	computed	Users with at least one membership row

A user joins a team via a TeamMember row carrying the user’s role (lead / owner / admin / member). One user can belong to many teams; one team can include many users.

Creating a Team

pfai team create "Backend" --identifier BACK
# Add and modify team members via the web UI or the team-members REST API
# (POST /api/v1/teams/{id}/members, PATCH /api/v1/teams/{id}/members/{userId})

Scoping Work to Teams

Once teams exist, work can be scoped in several ways:

• Projects — assign a project to a team. The project appears in that team’s sidebar section.
• Sprints — scope a sprint to a team so only that team’s issues and members are shown.
• Issues — filter any issue list by team to see only issues assigned to team members.
• Roadmaps — filter the roadmap by team to focus on that team’s projects and initiatives.

Team Switching

Switch your active team context from the team selector in the sidebar:

• Selecting a team filters the sidebar, dashboards, and default views to that team’s work.
• Select All Teams to remove the filter and see everything.
• Your last-selected team is remembered across sessions.

Custom Views

A custom view is a saved combination of filters, sorting, and grouping applied to the issue list. Views let you answer recurring questions without rebuilding filters every time.

Creating a View

1. Open the issue list and apply your desired filters (status, priority, assignee, label, sprint, etc.).
2. Choose a sort order and optional grouping (e.g., group by status).
3. Click Save View and give it a name.

View Visibility

Every view is scoped to one team and either personal or shared (per the isShared flag on the View model):

• Personal Views (isShared: false) — visible only to the creator. Use for your own workflow like “My open issues” or “Things I’m reviewing”.
• Shared Views (isShared: true) — visible to every member of the view’s team. Useful for shared dashboards like “Sprint board” or “Bug triage queue”. Only the creator and team leads/owners can edit a shared view; other members can use it but not modify.

There is no separate organization-level visibility — for a view that needs to span teams, build it on each team and pin them together in the sidebar. See the dedicated Views page for the full schema and CLI.

Example Views

View Name	Filters	Grouping
My Open Issues	Assignee = me, Status != Done/Cancelled	Priority
Sprint Board	Sprint = current, Team = active team	Status
Bug Triage	Label = bug, Status = Backlog or Todo	Priority
Unassigned Work	Assignee = none, Status != Done	Project
Overdue Items	Due date < today, Status != Done	Assignee

Managing Teams

Team leads and organization admins can:

• Add or remove team members.
• Rename or archive the team.
• Manage the team’s shared views.
• View team-level sprint statistics and velocity trends.

Archived teams are hidden from the team selector but their historical data (sprints, velocity) is preserved.