Integrations

GitLab + Outcome

GitLab holds your issues, merge requests and deployments. Outcome holds the goals they serve. Together, every issue and epic sits under a goal, delivery speed is read from GitLab's own records, and a decision becomes a new issue.

PreviewEngineeringStructureMeasuresSignalsWorkWrite-back

What each brings

GitLab brings the facts. Outcome turns them into decisions.

UseFrom GitLabWhat Outcome does with it
Structure
  • Groups, subgroups and projects
Each goal gets an owner, and each piece of work a team.
Measures
  • Merge requests merged and cycle time, by week
  • GitLab's DORA figures on Ultimate, or deployments and the failed share
A goal's number is read on a schedule, with its history.
Signals
  • Service Desk requests, without the sender
Grouped into themes and put in front of the goal they bear on.
Work
  • Issues, epics, merge requests and deployments
Placed under the goal it serves, so a goal with nothing behind it shows.
Write-back
  • A new issue, signed by whoever approved it
A decision becomes an item in the team's own tool, signed by whoever approved it.
Works well with

GitLab + PagerDuty + Atlassian + GitHub Copilot usage + Outcome

What it never reads
  • Source files
  • CI variables and secrets
  • Job logs
  • Changes to anything already in GitLab
Status

Preview Engineering

Live In the product today. Preview Working, refined with customers.

Setting it up

Connected in minutes, by an admin.

  1. 01Open

    An owner or admin opens Settings, Integrations, GitLab.

  2. 02Connect

    Paste: Access token.

  3. 03Read

    Outcome reads it on the schedule you set, from the first day.

  4. 04Send

    Work goes to GitLab only when a person approves it.

Full setup guide for customers

Connect GitLab and see what it brings in on the first sync.

Also in engineering Atlassian · GitHub · File import · Sentry · ServiceNow · PagerDuty · Azure DevOps · Linear