Skip to content

Keep engineering work and the conversation about it together

Sync GitHub issues and pull requests onto boards, with check results and review decisions on each card. Link cards to the relevant conversation and use the team's existing roles. The API, webhooks and slash commands support additional automation.

Updated

engineering

A card and its issue

Enclessa card

  • Checks passing · review approved
  • Pull request attached
  • Linked to the message it came from

GitHub issue

Status field of a Projects v2 project, mapped to the board columns.

With Boards and GitHub

Connect engineering work to the conversation in Enclessa

  1. Put the team, its channels and its board in one place

    A board belongs to a team and uses that team’s roles, so the people who can see the channel are the people who can see the work.

  2. Connect the repository once, at the organisation level

    An administrator makes one connection with a GitHub App or a personal access token, and it covers GitHub.com or GitHub Enterprise Server.

  3. Map the columns to the project status

    Board columns map onto the Status field of a GitHub Projects v2 project, so moving a card and moving a project item mean the same thing rather than two things that have to be reconciled.

  4. Let pull requests attach to the work they finish

    A pull request that closes an issue attaches to that issue’s card instead of becoming a second card, and the card shows the check rollup and the review decision.

  5. Decide deliberately whether Enclessa may write back

    Write-back to GitHub is a per-organisation setting. Leave it off and the connector reads; turn it on and moving a card moves the project item.

  6. Create work from the conversation that produced it

    When a discussion in a channel turns into work, make the card from the message.

Connecting a GitHub repository to a board
One connection, made once per organisation.
  • The decision and the ticket are in different products
  • The board is a second, worse copy of the repository
  • A second permission model to keep in step
  • Checking the build means leaving
A board in table view with filters on status, owner and due date
Source of truth
GitHub for code, Enclessa for the work and the talking
Sync
Issues and pull requests, in both directions when enabled
On the card
Check rollup, review decision, the linked pull request
Provenance
A card links back to the message it came from
Permissions
Boards inherit the team’s roles

Which plan this needs

Boards and the GitHub connector are both on the Team plan and above, and GitHub requires Boards because the things it syncs are board cards.

Compare plans

What it will not do

The limits, before you find them

  • GitHub, GitLab (GitLab.com or self-managed), Forgejo and Gitea are supported.
  • Enclessa does not host code, run pipelines or review diffs.
  • Boards have no dependencies, sub-items, automation rules, cross-board views or reporting charts.
  • There is no event stream out of the platform, so tooling that wants to react to something happening in Enclessa has to poll for it.

FAQ

Engineering work in one place: questions

  • No. Code, pull requests and pipelines stay in GitHub. Enclessa syncs the issues and pull requests onto a board, shows the check rollup and review decision on the card, and keeps the conversation about the work in the same product.

  • Yes. A board card carries a link to the channel and the message the work came out of, which is the part a separate project tool cannot do.

  • No. A board belongs to a team and inherits that team’s roles, so the people who can see the channel are the people who can see the work, and there is no second permission model to keep in step.

Bring your team over this afternoon

Free for up to 10 people, with encrypted direct messages and video calls. No payment card, no time limit, no server to run.

For businesses and organisations only — not available to consumers.

Create your organisationCompare plans