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
Section titled “Assigning a ticket”When you assign a Jira ticket to Bucky, the agent:
- Reads the ticket description and context
- Identifies the target repository (from the ticket or by asking)
- Creates a GitHub issue with a link back to the Jira ticket
- Dispatches a Claude session in plan mode
The GitHub issue title includes the Jira key prefix (e.g., AD-1234: Implement retry logic) and the body contains a Jira Context section with a link back to the ticket.
Commenting on a ticket
Section titled “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.
Webhook endpoints
Section titled “Webhook endpoints”| Endpoint | Purpose |
|---|---|
POST /webhooks/jira | Ticket assignments |
POST /webhooks/jira/comments | Ticket comments |
Both endpoints share the same authentication (webhook secret) and session management. The agent uses the jira:<issueKey> session index to maintain continuity.
Session linking
Section titled “Session linking”When Bucky creates a GitHub issue 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