Skip to main content
Connect Jira and Confluence to your codebase with a single automation. When a Jira ticket is moved to a ready state (or @devin is mentioned in a comment), this automation reads the full ticket — linked Confluence docs, acceptance criteria, comments — and implements the change as a pull request against the right repo.

Use this template

Open Jira Ticket to PR in Devin and create the automation with the default configuration. You can customize it before saving.

​
What this automation does

The Atlassian MCP gives Devin first-class access to Jira and Confluence, so tickets aren’t just titles and descriptions — they’re full contextual bundles. Devin pulls the linked architecture doc, reads the sub-tasks, checks the linked epic, and only then starts coding.

​
How it works

Trigger: Slack event — message
  • Event: slack:message
    • Conditions:
      • channel eq #dev-requests
What Devin does: Starts a session with full event context, executes the prompt below, and (optionally) notifies you on failure.

​
Prerequisites

​
Example prompt

The template ships with this prompt. You can edit it after clicking Use template, or leave it as-is.

​
Setting it up

  1. Open Automations → Templates in Devin.
  2. Click Jira Ticket to PR. The create page opens with this template pre-filled.
  3. Connect any required integrations and install MCP servers if you haven’t already.
  4. Replace any placeholder values in the trigger conditions (for example, swap your-org/your-repo for your actual repo).
  5. Review the prompt and adjust it for your team’s language, conventions, and guardrails.
  6. Click Create automation.
Most automation templates include suggested ACU and invocation limits to bound cost during early rollout. Keep them as-is until you’re confident in the automation’s behavior, then raise them to fit your workload.

​
When to use this template

  • Enterprise teams running on Atlassian’s stack
  • Teams with heavy Confluence documentation that needs cross-referencing
  • Bridging the gap between product management (Jira) and engineering delivery
  • Async-first teams where tickets can run ahead of a human picking them up

​
Customization ideas

  • Match on specific Jira projects, labels, or workflow transitions
  • Read from a specific Confluence space for context
  • Route to different repos based on Jira components or labels
  • Attach a playbook that encodes your team’s implementation conventions

​
See also