
Features
- Add the
Tembolabel to trigger implementation - Use
tembo/{repo-name}labels to target specific repositories - Status updates and PR links posted as comments
Installation
Create Tembo account
Create a dedicated Jira account for Tembo using an email alias (
you+tembo@company.com) or dedicated email.Install
Go to Integrations and click Install next to Jira. Log in as the Tembo account.
Usage
Add theTembo 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 formattembo/{repo-name} (for example, tembo/monorepo).
{repo-name}must match the repository name as it appears in Tembo (thenamefield on the connected repository).- The
tembo/prefix is case-sensitive: use lowercasetembo/. - Valid characters in
{repo-name}are letters, numbers,_,., and-.
tembo/{repo-name} labels are present, Tembo uses the first one that matches a connected, enabled repository.
Fallback behavior
If notembo/{repo-name} label matches a connected, enabled repository, Tembo falls back in this order:
- The default repository configured for your Jira integration in Tembo
- The first available enabled repository in your Tembo organization
Automations
See Automations for available Jira event triggers.Advanced
Tembo not responding to labels
Tembo not responding to labels
Verify the issue has a
Tembo label or a tembo/{repo-name} label (for example, tembo/monorepo). Confirm you installed using the dedicated Tembo Jira account. Check integration status on the Integrations page.Issues not being processed
Issues not being processed
Ensure GitHub/GitLab/Bitbucket is connected. Include clear descriptions with acceptance criteria.