Jira Integration
Trigger tasks and pull context from Jira Cloud issues.
Ryven integrates with Jira Cloud to accept signals from issue events and pull ticket context into tasks — the same way it works with Slack and GitHub issues.
Setup
- Go to Settings > Integrations in the Ryven dashboard
- Click Connect Jira
- Authorize access to your Atlassian account
- Select the Jira site and projects to connect
Ryven registers webhooks on your selected projects to receive issue events automatically.
What context Ryven pulls from a ticket
When a task is triggered from Jira, Ryven reads:
- Summary — the ticket title
- Description — the full ticket body
- Comments — discussion and clarifications from the team
- Acceptance criteria — if included in the description or a custom field
This context is stitched into the agent's prompt alongside any other linked signals (e.g., a Slack thread referencing the same ticket).
Example workflow
- A Jira issue event fires on a connected project
- Ryven receives the webhook and creates a task
- It reads the ticket summary, description, and comments
- The agent clones the repo, writes the code, and opens a PR
- The PR body links back to the Jira ticket for traceability
Identity mapping
For Jira-triggered tasks to be attributed to the correct workspace member, each member should link their Jira account:
- Go to Settings > Profile > Linked Identities
- Click Link next to Jira
- Authorize the connection
This maps your Jira user ID to your workspace membership. If a member hasn't linked their account, the task is still created but may not be correctly attributed.
In the dashboard
Tasks triggered from Jira show Jira as the trigger source in the Runs list. The task detail view includes the Jira ticket reference for full traceability back to the original ticket.