Integrations

Atlassian + Outcome

Jira holds the work and Confluence holds the plans. Outcome adds the goal each piece of work serves. Together, every epic sits under the goal it moves, a goal with nothing behind it shows, and a decision becomes a Jira issue in the right project.

LiveEngineeringStructureGoalsWorkWrite-back

What each brings

Atlassian brings the facts. Outcome turns them into decisions.

UseFrom AtlassianWhat Outcome does with it
Structure
  • Atlassian teams
Each goal gets an owner, and each piece of work a team.
Goals
  • Atlassian goals, with their status
  • Goals written in Confluence plans, proposed with their source line
They arrive as proposals, and a person accepts each one.
Work
  • Jira issues and epics, with status, estimates and dates
Placed under the goal it serves, so a goal with nothing behind it shows.
Write-back
  • A new Jira issue in the project you choose, from a decided gap
A decision becomes an item in the team's own tool, signed by whoever approved it.
Works well with

Atlassian + TeamForm + GitHub + PostHog + Outcome

What it never reads
  • Pages and projects the connected account cannot see
  • Anything beyond keys, titles, status and dates, when you choose names only
  • Changes to anything already in Atlassian
Status

Live 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, Atlassian.

  2. 02Connect

    Sign in with Atlassian and approve the access it asks for.

  3. 03Read

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

  4. 04Send

    Work goes to Atlassian only when a person approves it.

Full setup guide for customers

Where it is used

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

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