Skip to main content
Keep your team in Jira while Revolte carries a ticket from ready-to-build work to a reviewable code change. Need every screen and setting? The detailed Jira Workflow guide walks through the complete configuration.
Before you start: Have permission to install the Revolte app in Jira and a repository you can connect to a Revolte application. If the repository is not connected yet, the setup flow will guide you through it.
1

Open Autopilot and Connect Jira

In Revolte, open Chat and select Autopilot. Install the Revolte app from the Atlassian Marketplace, approve the requested permissions, and choose the Atlassian site your team uses.
The Revolte Autopilot setup screen for connecting a Jira workspace.
For the complete connection flow, see Connect Jira.
2

Finish the Application Setup

Complete the remaining setup checks:
  1. Git Integration connects the repository Revolte will work in.
  2. Configure Application records the application’s service details.
  3. Commit YAML saves the revolte.yml configuration.
When all four setup items show a green checkmark, select Configure workflow.
The setup checklist completed with a Configure workflow action.
3

Choose Which Jira Tickets Revolte Should Handle

Open Automation Configurations and select Configure Automation. Then choose:
  • Workflow: Select Developer workflow.
  • Status mapping: Choose the Jira status that starts work, such as To Do, and the statuses used while work is in progress and complete.
  • Target branch: Choose where Revolte should propose its changes, such as qa or main.
  • Model: Select a model that fits the task—for instance, Claude Haiku - Fast & efficient.
The Configure Workflow Automation form with Jira status mapping, branch, and model settings.
Save the configuration. It will appear in the active configurations list with its branch and status flow.
4

Start the Workflow from a Jira Ticket

Open the ticket in Jira and find Revolte in the right sidebar. Under Select Application, choose the application Revolte should update.
A Jira ticket with the Revolte panel and Select Application control in the right sidebar.
The panel will show Workflow Triggered. Select View Workflow Details to open the live run. See Triggering workflows from Jira for more detail.
5

Follow the Agent Run

In Revolte, open Agent runs to follow the workflow status. When the run completes, open it to review stages such as Sandbox Provisioning, Code Setup, and Token Usage.
A completed agent run showing its execution stages and summary.
Revolte performs the work in an isolated sandbox, keeping the run separate from your local machine and shared environments.
6

Review the Plan and Code Changes

Open Artifacts to read the implementation plan, subtasks, and proposed file changes. Then open Diff Summary to compare every line the agent created or modified.
The Diff Summary view showing files and code changes produced by the agent.
Review the result before it moves into your normal delivery process.
7

Review the Pull Request and Preview

When the agent finishes, Revolte opens a pull request in GitHub or your configured Git provider. Review the proposed changes with your team, then merge when they are ready.
A pull request created from a completed autonomous workflow and ready for review.
After merging, select View Preview to validate the deployment using your revolte.yml configuration.✓ Your first autonomous workflow is complete. The Jira ticket has moved through implementation, code review, and delivery without leaving your team’s existing workflow.

​
Next steps