# Introducing Rovo Dev in Jira | Rovo Dev | Atlassian

Source: https://www.youtube.com/watch?v=tEbCO3wG_vQ
Recap page: https://rapidrecap.app/video/tEbCO3wG_vQ
Generated: 2025-11-17T12:03:53.86+00:00

---
## Quick Overview

Rovo Dev integrates directly into Jira, leveraging the Rovo Dev CLI in the cloud to generate boilerplate code for a Jira work item, such as building a new React app for Team 25, by inferring context from the issue description and automatically creating and pushing a new branch for development.

**Key Points:**
- Rovo Dev allows users to leverage the power of Rovo Dev CLI in the cloud directly from a Jira ticket to generate initial code for development.
- The process begins by selecting the "Generate code" option within a Jira work item (e.g., ADTEAM-781: Build a new app for Team '25').
- The user selects the target repository (e.g., mcolman/new-react-app) and Rovo Dev automatically infers context from the Jira issue description to set up the code generation.
- Code generation settings allow customization of the branch name (defaulting to a pattern like {issuekey}-{issuesummary}) and source branch.
- After code generation, Rovo Dev creates a cloud session, generates the required code files (like App.js, App.css, index.html), and pushes the changes to a new branch.
- The system automatically updates the Jira work item status to 'In Review' upon detecting the associated pull request creation, as demonstrated by the PR titled 'First changes to my app for Team 25'.
- The interface allows users to review generated files, accept changes, or interact with the generated code within the cloud IDE environment.

![Screenshot at 00:31: The user triggers the Rovo Dev code generation process from the Jira ticket by clicking 'Generate code' after confirming the work item context.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-00-31.png)

**Context:** This video demonstrates the integration between Rovo Dev, an AI-powered development assistant, and Jira, focusing on how developers can initiate coding tasks directly from a Jira ticket using Rovo Dev's cloud capabilities. The specific task demonstrated is creating a new React application for 'Team '25' as defined in the Jira issue ADTEAM-781, showing how context is extracted and code is scaffolded automatically.

## Detailed Analysis

The demonstration showcases Rovo Dev's capability to bridge Jira work items with cloud-based development sessions. Starting from a Jira ticket titled 'Build a new app for Team '25', the presenter initiates code generation using Rovo Dev, which automatically reads the issue description detailing requirements like using create-react-app, styling with Atlassian brand colors, and setting task statuses (To Do, In Progress, Done). The user selects the repository and triggers code generation (00:49), which results in the automatic creation of a development session (01:34) and the generation of boilerplate code in the cloud IDE (01:37). Rovo Dev automatically configures the branch name and attaches the Jira work item to the changes. Once the code is generated and reviewed, the user creates a pull request in Bitbucket (02:45) with an auto-populated title and branch name, which, upon creation, triggers automation back in Jira to change the work item status to 'In Review' (03:10). The video concludes by showing the session list, confirming the active session, and highlighting the tight integration between planning (Jira) and coding (Rovo Dev).

### Rovo Dev Initialization

- Leveraging Rovo Dev CLI in the cloud
- Triggering code generation from Jira ticket ADTEAM-781
- Selecting the 'mcolman/new-react-app' repository

### Code Generation Process

- Repository access confirmed
- Branch name pattern set to {issuekey}-{issuesummary}
- Context inferred from Jira issue description

### Session Creation & Code Output

- Cloud session created successfully (01:34)
- IDE shows 'Generating your code'
- Initial files generated include App.js, App.css, and index.html

### Jira Automation

- Work item status automatically updated to 'In Review' upon pull request detection (03:10)
- Pull request 'First changes to my app for Team 25' detected and linked

### Post-Generation Workflow

- Reviewing generated files in the IDE
- Option to create a Git commit or Pull Request directly from the IDE interface
- Final confirmation of linked PR in the Development ADTEAM-781 view

![Screenshot at 00:05: The Jira board view showing the active sprint and various work items, setting the context for the task selection.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-00-05.png)
![Screenshot at 00:31: The user clicks 'Generate code' within the Jira issue view, initiating the Rovo Dev AI coding process.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-00-31.png)
![Screenshot at 00:48: The 'Generate code' modal, showing the selected repository and the work item linked for context inference.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-00-48.png)
![Screenshot at 01:12: The 'Code Settings' modal overlay, where the user can customize the branch name and source branch before generation.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-01-12.png)
![Screenshot at 01:34: Confirmation toast indicating 'Session created successfully' as the cloud environment is provisioned.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-01-34.png)
![Screenshot at 01:41: The cloud development environment loading, displaying the initial prompt about generating code.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-01-41.png)
![Screenshot at 02:17: The AI-generated code reflected in the file explorer and editor panes within the cloud IDE, showing file changes.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-02-17.png)
![Screenshot at 02:35: The prompt in the IDE suggesting next steps, including creating a Git commit or Pull Request.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-02-35.png)
![Screenshot at 02:46: The Bitbucket 'Create a Pull Request' screen, showing the branch details automatically populated from the Rovo Dev action.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-02-46.png)
![Screenshot at 03:10: The Jira work item details showing the status automatically transitioned to 'In Review' after the pull request was detected.](https://ss.rapidrecap.app/screens/tEbCO3wG_vQ/00-03-10.png)