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.
GitLab brings the facts. Outcome turns them into decisions.
| Use | From GitLab | What Outcome does with it |
|---|---|---|
| Structure |
| Each goal gets an owner, and each piece of work a team. |
| Measures |
| A goal's number is read on a schedule, with its history. |
| Signals |
| Grouped into themes and put in front of the goal they bear on. |
| Work |
| Placed under the goal it serves, so a goal with nothing behind it shows. |
| Write-back |
| A decision becomes an item in the team's own tool, signed by whoever approved it. |
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.
Connected in minutes, by an admin.
- 01Open
An owner or admin opens Settings, Integrations, GitLab.
- 02Connect
Paste: Access token.
- 03Read
Outcome reads it on the schedule you set, from the first day.
- 04Send
Work goes to GitLab only when a person approves it.
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