Skip to main content

​
Setting up the integration

  1. In your Devin account at app.devin.ai, go to Settings > Integrations > Jira, and click “Connect”.
  2. You’ll be redirected to Jira to review permissions and grant Devin access.
  3. Once connected, configure your playbook labels and optionally set up automation triggers in the settings page.
After connecting, we recommend connecting a service account so Devin’s comments appear as the bot, not as your personal account. See Connecting a service account below.

​
How to trigger Devin from Jira

There are four ways to start a Devin session from a Jira ticket:

​
Assign the ticket to Devin

Assign the ticket to the Devin service account directly in Jira. Devin will use the default playbook configured in your Jira integration settings to start working on the ticket.

​
Add a playbook label

Add a playbook label (e.g. !plan, !implement, !triage) to the ticket. Devin will start a session using the specific playbook that matches the label. These labels correspond to the playbook labels configured in your integration settings. You need to create these labels manually in your Jira project — copy the label name from the integration settings.

​
Add the “devin” label

Add the devin label to any Jira issue (you may need to create this label in your Jira project first). Devin will use the default playbook to start working on the ticket.
The integration uses word-boundary matching (case-insensitive), so any label containing devin as a standalone word will trigger it — for example, devin, Devin, devin-workshop, or devin-task. Labels where “devin” is part of a larger word, like devinworkshop or devin_workshop, will not trigger it.

​
@mention Devin in a comment

Mention @Devin in a ticket comment with specific instructions. Devin will start a session and use your comment as the task instruction, without applying a playbook. If a session already exists for the ticket, your message will be forwarded to the existing session.

​
Configuring the integration

​
Session mode

The session mode toggle controls how Devin responds to Jira triggers:
  • Direct session creation (enabled by default): Devin creates a full session and works on the issue, posting updates back to Jira.
  • Scoping only (disabled): Devin only analyzes the ticket and posts a scoping comment with a summary, implementation plan, and confidence estimate. You can then click the provided link to start a session manually.

​
Playbook labels

Playbook labels let you control which Devin playbooks are available as Jira labels. When you add a playbook, its macro (e.g. !plan) becomes a label you can assign to Jira issues to trigger Devin with that playbook. Labels must be created manually in your Jira project — copy the label name from the integration settings.
  • Default playbook: One playbook is marked as the default. When a ticket is triggered without a specific playbook label (e.g. with just the devin label or by assigning the ticket to Devin), Devin uses this default playbook.
  • Adding playbooks: Click “Add playbook” to add additional playbooks. Only playbooks with a macro can be added.
  • Removing playbooks: Remove a playbook to stop using its label as a trigger.

​
Automation triggers

Automation triggers let Devin automatically start working on tickets when they match certain conditions, without manual assignment or labeling. You can configure triggers based on:
  • Projects: Only trigger for tickets in specific Jira projects.
  • Labels: Only trigger when a ticket has specific labels.
  • Statuses: Only trigger when a ticket reaches a specific status (e.g. “To Do”, “In Progress”).
  • Playbook: Optionally specify which playbook Devin should use for the triggered session.
Triggers use edge detection, meaning they only fire when a ticket transitions from not matching to matching the trigger conditions (e.g. when a label is added or a status changes), not for tickets that already match.

​
Enterprise: Jira project mapping

For enterprise deployments with multiple Devin organizations, admins can map Jira projects to specific Devin organizations. This ensures tickets from each Jira project are routed to the correct Devin organization. A mapping is required for the Jira integration to work in enterprise setups.

​
Interacting with Devin in Jira

Once Devin starts working on a ticket, it communicates back through Jira:
  • PR links: When Devin creates a pull request, the PR URL is automatically added as a remote link on the Jira issue and posted as a comment.
  • Session link: A direct link to the Devin session in the web app is provided so you can follow progress in real time.
  • Follow-up messages: Mention @Devin in a comment to give Devin additional instructions or ask questions.

​
Connecting a service account

After connecting Jira with your admin account, you can optionally connect a service account using OAuth 2.0 client credentials. This makes Devin’s comments appear under a dedicated bot identity instead of your personal account.
  1. In your Atlassian organization’s admin settings, create an OAuth 2.0 service account with the following Classic scopes:
    • read:me
    • read:jira-user
    • read:jira-work
    • write:jira-work
  2. In Settings > Integrations > Jira, click Connect service account and enter the client ID and client secret.