Set up your team

Stand up a Pulse team — join or create it, then configure workflow and how work is grouped.

Guidance for standing up a team in an existing workspace, or for joining one that is already running.

Learn the core concepts

Concepts covers workspace, team, issue, and how projects and initiatives relate. Read that first if you are new to Pulse, then come back here to configure a team.

Join or create a team

Workspace managers and platform admins create teams from Settings → Administration → Teams (Create team), or from Create a team… in the command menu (Cmd/Ctrl K).

To join an existing team, a team manager adds you from Settings → Your teams → <team> → Members (Add members). Workspace admins invite people to the workspace from Settings → Administration → Members first; then someone adds them to the team.

You do not have to join every team you can open issues on. Workspace-wide availability (Service provider) can show a team in pickers to all workspace members.

Teams you belong to appear in Your teams. See Teams for hierarchy, sub-teams, and archive.

Get familiar with your team's workflow

Open Settings → Your teams → <team> from Go to → Team settings on team Home, or from the row menu on Settings → Administration → Teams.

This is the best way to see how the team operates, including:

  • Issue status in Issue statuses — the workspace workflow every team uses (Backlog → Done)
  • Cycles in Cycles — enable a repeating time-box when the team wants one
  • Templates in Templates — issue, project, and request presets for this team
  • Labels in Team labels
  • Estimates in General
  • Request triage and related request settings when Requests is on

Issue statuses are workspace-wide. Cycles, labels, and templates are easy to keep per team.

Configure notifications and Inbox

By default you are subscribed to work you are assigned, own, comment on, or are mentioned on. Those updates go to Inbox (G then I).

Tune Email, Mattermost, and Push from Settings → Notifications. Inbox is not the Pulse feed — Pulse lists initiative and project status updates.

Connect your accounts

From Settings → Connected accounts (/settings/applications) you can connect a personal GitHub or GitLab identity for Reviews, and revoke apps that can access your Pulse account. That page is not the workspace Applications catalog.

See Profile, GitHub, and GitLab.

Use keyboard shortcuts

Common chords after you join:

  • C — create an issue
  • Cmd/Ctrl K — command menu
  • Cmd/Ctrl / — shortcuts sheet
  • G then E — team Issues; G then I — Inbox; G then M — My issues; G then S — Settings

If you want to do something and are not sure how, search the command menu.

Favorite pages you reopen

Pin issues, projects, views, and other pages you open often. Favorites sit in the sidebar under personal shortcuts. Press Option/Alt F on a page that has a favorite control, or use the star on the entity.

See Favorites. Explore existing views under the team and in the Workspace Views list to see how the team already slices work.

Handle incoming requests

Teams often review incoming work in Triage under the team (G then T) before it becomes delivery. A request is intake — not an issue. Linking a request to an issue keeps both.

Check team Templates for standard request or issue shapes, and workspace Customer requests under Features when intake is enabled.

Start with issues

For a new team, create issues as soon as you have work — bugs, features, tasks, and stories. Pulse issues are not Stories and Epics as project children; those are issue types on a team backlog.

Use sub-issues when a set of work is too large for one issue and too small for a project. You can convert later into a project when the scope grows.

Plan with projects and initiatives

When work spans many issues, create a project. Set Start and Target dates when you know them, add milestones for stages, and post status updates.

Status is the project's lifecycle (Idea, In Progress, Completed, …). Health is On Track, At Risk, or Off Track, from the latest project update. They are different fields. Move finished work to Completed (or Canceled).

When several projects share one outcome, create an initiative. Give it a Lead team. Initiative status is Proposed, Planned, Active, Completed, or Canceled. Initiative health is On Track, At Risk, or Off Track, from the latest initiative update. An active initiative can still be At Risk. See Initiatives.

Last updated on