Skip to main content

Documentation Index

Fetch the complete documentation index at: https://test-8862363a-tembo-enforce-user-limit-10-with-override.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Jira

​
Features

  • Add the Tembo label to trigger implementation
  • Use tembo/{repo-name} labels to target specific repositories
  • Status updates and PR links posted as comments

​
Installation

1

Create standard Jira user

Create a dedicated standard Jira user for Tembo using an email alias (you+tembo@company.com) or dedicated mailbox. In the Jira user profile, set the name/display name to Tembo so integration comments show up as Tembo.
2

Install

Go to Integrations and click Install next to Jira. Log in as the standard Jira user.
3

Add labels

Create a Tembo label in your Jira project (recommended). Add it to any issue you want Tembo to work on.

​
Usage

Add the Tembo label to any issue. Tembo reads the description, creates a coding session, and opens a PR. If you add a tembo/{repo-name} label, that also triggers Tembo and routes the task to the selected repository.

​
Target a specific repository

Add a label in the format tembo/{repo-name} (for example, tembo/monorepo). This label also triggers processing on its own, so you do not need a separate Tembo label.
  • {repo-name} must match the repository name as it appears in Tembo (the name field on the connected repository).
  • The tembo/ prefix is case-sensitive: use lowercase tembo/.
  • Valid characters in {repo-name} are letters, numbers, _, ., and -.
When multiple tembo/{repo-name} labels are present, Tembo uses the first one that matches a connected, enabled repository.

​
Fallback behavior

If no tembo/{repo-name} label matches a connected, enabled repository, Tembo falls back in this order:
  1. The default repository configured for your Jira integration in Tembo
  2. The first available enabled repository in your Tembo organization

​
Agents

See Agents for available Jira event triggers.

​
Advanced

Verify the issue has the Tembo label or a tembo/{repo-name} label (for example, tembo/monorepo). Confirm you installed using the dedicated standard Jira user. Check integration status on the Integrations page.
Ensure GitHub/GitLab/Bitbucket is connected. Include clear descriptions with acceptance criteria.