Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 23 additions & 6 deletions integrations/jira.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ description: "Assign tickets to Tembo and get PRs back."

## Features

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

Expand All @@ -23,25 +23,42 @@ description: "Assign tickets to Tembo and get PRs back."
Go to [Integrations](https://app.tembo.io/integrations) and click **Install** next to Jira. Log in as the Tembo account.
</Step>
<Step title="Add labels">
Create a "Tembo" label in your Jira project. Add it to any issue you want Tembo to work on.
Create a `Tembo` label in your Jira project (recommended). Add it to any issue you want Tembo to work on.
</Step>
</Steps>

## Usage

Add the "Tembo" label to any issue. Tembo reads the description, creates a coding session, and opens a PR.
Add the `Tembo` label to any issue. Tembo reads the description, creates a coding session, and opens a PR.

To target a specific repo, add a `tembo/{repo-name}` label (e.g., `tembo/frontend`).
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`).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a nice addition. I’d make it explicit that tembo/{repo-name} also triggers processing by itself so readers don’t think they need both labels.

Suggested change
Add a label in the format `tembo/{repo-name}` (for example, `tembo/monorepo`).
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

## Automations

See [Automations](/features/automations) for available Jira event triggers.

## Advanced

<AccordionGroup>
<AccordionGroup>
<Accordion title="Tembo not responding to labels">
Verify the label is exactly "Tembo" (case-sensitive). Confirm you installed using the dedicated Tembo Jira account. Check integration status on the [Integrations page](https://app.tembo.io/integrations).
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](https://app.tembo.io/integrations).
</Accordion>

<Accordion title="Issues not being processed">
Expand Down