Integrations settings

The Integrations tab connects the current workspace to the services around your code: one issue tracker, SonarCloud and Slack. Every setting here applies to this workspace only. Each service has its own guide under Integrations; this page says what each section of the tab holds.

#Issue tracker

Issue tracker links each pull request to its tickets. Each workspace has its own tracker, or none. Choose a Provider: None, Jira, GitHub Issues, Linear or Notion.

• GitHub Issues: a pull request’s tickets are the issues it closes (“Fixes #12”) or an issue linked in its Development panel. Nothing to set up. When a repository uses GitHub Issues and no choice is saved, Limn picks it automatically and says so. See GitHub Issues.
• Jira: enter your Jira site. A ticket key such as PAY-142 is found in the pull request title, and in the branch name if you choose. Project keys stop false matches such as GPT-4 or node-18; without them only the title is read. See Jira.
• Linear: enter your Linear workspace address. Issues that Linear’s GitHub integration attached to the pull request are always found; other keys count only if their team is in Team keys. See Linear.
• Notion: tickets are the pages of one database, found by their Unique ID (such as ENG-123). Paste the database link, then map its properties. See Notion.

Where to look is PR title only or PR title and branch name (default). The branch is read only when you have set keys. Commit messages are never read.

Reading the tickets

To show a ticket’s title, status, assignee, description and acceptance criteria, Limn needs read access:

• Jira API access (optional): the Email and an API token (a Jira Cloud API token, or a Data Center personal access token with the email left blank). Select Check connection.
• Personal API key for Linear: create one in Linear under Settings → Security & access. Read access is enough.
• Integration token for Notion: an internal integration with read content, read comments and read user information, shared with the database.
• GitHub Issues uses your GitHub sign-in.

Ticket fields

Jira sites often have several fields called “Acceptance Criteria”, and each issue type can use a different one. Once a token is saved, a table lists each issue type with a Criteria menu and an Open points menu. Limn picks uses the field whose name best matches. Open points are what the ticket left undecided; a review lists them with the code that depends on them, and they never block it. A change applies at once to every stored ticket of that type. See Acceptance criteria.

#SonarCloud

Feed SonarCloud’s findings into AI Review and AI Fix. Create a token in SonarCloud under My Account → Security, then enter the Organization key and the token. Each repository’s project key defaults to SonarCloud’s own; type one only if yours differs. Select Test connection: each repository shows Found or Not found. Limn only reads. See SonarCloud.

#Slack

Sends this workspace’s Pending board, a sprint summary, merges and auto reviews to a Slack channel.

• Incoming webhook URL: create one at api.slack.com/apps → Incoming Webhooks.
• Cadence: Off (paused, channel kept), Daily or Twice daily, with Send at and And at.
• Include a review-bot summary: each review bot’s comment count, the share your team used and the number left untouched.
• Post when an auto review finishes and Post when a pull request merges: off until you switch them on. Reviews you start yourself are never posted to Slack.
• Send test sends a message now.

See Slack.