Jira

Bucky integrates with Jira via webhooks. You can trigger him by assigning a ticket or commenting on one he’s already working on.

Assigning a ticket

When you assign a Jira ticket to Bucky, the agent:

1. Reads the ticket description and context
2. Identifies the target repository (from the ticket or by asking)
3. Creates a dashboard session linked to the Jira ticket
4. Dispatches a Claude session in plan mode

Commenting on a ticket

Comment on a Jira ticket that Bucky is working on to provide follow-up context or instructions. Comments are routed to the same ADK session as the original assignment, maintaining full conversation history.

Note

Bucky filters out his own comments to avoid self-triggering loops.

Session linking

When Bucky creates a dashboard session from a Jira ticket, both are linked to the same session. This means:

• Comments on the Jira ticket are seen by the same agent session
• Workflow callbacks (plan completed, PR opened) are posted back to the Jira ticket
• The agent has full context from both platforms when reasoning about next steps