Generate code from a work item in Jira
When Rovo Dev in Jira is enabled on your site, a Rovo Dev section will appear on work items. Use Rovo Dev to generate code directly from the work item based on its details.
はじめる前に
To use Rovo Dev in Jira, make sure:
Rovo Dev is added to your Jira site; you can check this by going to
{yoursite}.atlassian.net/rovodev.Rovo Dev in Jira is enabled at both the organization level and the site level.
You have available Rovo Dev credit allowance. How to view your Rovo Dev credit usage
Bitbucket Cloud or GitHub Cloud is connected to your Jira site.
Generate code from a work item
When Rovo Dev in Jira is enabled on your site, a Rovo Dev section will appear on work items. To generate code based on the work item:
作業項目を開きます。
Select Generate code in the Rovo Dev section.
Select a repository where you want to generate the code. You can select multiple repositories if your work spans across those repositories. Rovo Dev will create a separate session per repository.
Enter a prompt or add a saved prompt from the repository to provide more context (like specific instructions you want to give Rovo Dev or additional references like code standards, important file paths and examples of similar changes).
Select the settings icon () to define code and environment settings for your Rovo Dev sessions. How to configure a Rovo Dev in Jira session
Select Generate code in draft pull request if you want Rovo Dev to create a pull request for the code changes it made.
When you select this option, it configures your code settings to let Rovo Dev push code changes to your branch and always create a draft pull request on your behalf, which you and your team can review and merge. Use the settings icon () to modify these code settings.
Select Generate code.
Rovo Dev starts working and generates code based on the work item and any extra context you added. Select the session to view the code (even while Rovo Dev is working).
Your Rovo Dev credits will be used to generate code.
Edit generated code
View and edit the code generated by Rovo Dev for your current session, or a previous session you were working on.
To edit code generated by Rovo Dev:
Go to your work item and open a Rovo Dev session.
Use the chat panel to ask Rovo Dev questions about the code, or ask Rovo Dev to make changes.
Highlight specific lines of code to let Rovo Dev know exactly which code you’re referencing in your chat message.
Select files to see the code difference. You can also edit code directly if you like.
Repeat the steps until you’re happy with the code.
Once done, you can commit code changes to a branch and raise a pull request. If you configured Rovo Dev to commit code to your branch and create a draft pull request on your behalf, it won’t merge the draft pull request directly, but will hand it back to your team for review and merge.
プル リクエストを作成する
Once you’re happy with your code, create a pull request. Or, if a pull request is already created, commit your changes to it.
To create a pull request:
In the chat panel, select Create pull request.
Enter a commit message.
Select Create pull request.
If you include your Jira work item key in the commit message or pull request description, the pull request will be automatically linked to the work item.
You (as the person using Rovo Dev in Jira) will be listed as the pull request author and author of any commits.
Manage Rovo Dev in Jira sessions
Rovo Dev in Jira sessions let you continue from where you left off by maintaining conversation history and context across multiple interactions.
Each session keeps its own message history and conversation context in the sandbox environment. Sessions are scoped to the Jira site you’re working in, and when you view all sessions, you’ll only see your own Rovo Dev in Jira sessions for that site.
To view your Rovo Dev in Jira sessions:
作業項目を開きます。
View sessions you created for that work item in the Rovo Dev section. Select a session to continue working on it.
Select View all sessions to see all your Rovo Dev sessions across the site.
Select a session to continue working on it or archive the session when you’ve completed your work. You can unarchive sessions later if needed.
What can Rovo Dev in Jira access?
Rovo Dev in Jira processes data in a secure, cloud-based coding session that runs inside a dedicated sandbox environment. Only the person who starts the Rovo Dev session (or runs the Generate code automation rule) can access that sandbox.
Rovo Dev in Jira can interact with Atlassian apps and your code to understand tasks and generate code changes. Specifically, it can:
perform create, read, update, and search operations (but not delete) in Jira and Confluence on the initiating user’s behalf, where the user has the required permissions
read from and write to connected code repositories, limited to the repository selected for the session
run Bash or PowerShell commands inside the secure sandbox environment
Rovo Dev in Jira acts strictly on behalf of the initiating user. It can’t exceed that user’s existing permissions and restrictions when accessing Atlassian apps and connected repositories. It is an autonomous agent and may perform these actions without asking for confirmation each time.
For each session, Rovo Dev in Jira clones only the selected repository into a secure sandbox. It doesn’t copy data from other repositories or your local file system, and any data deletion is limited to the sandbox.
Rovo Dev in Jira lets users choose whether it pushes code changes to a branch and creates a draft pull request on their behalf. It doesn’t merge pull requests. Your team remains in control of reviewing, approving, and merging any code that Rovo Dev generates, and users should carefully review all changes before merging them into their codebase.
Rovo Dev in Jira doesn’t connect to third-party data sources using Model Context Protocol (MCP)
Administrators can turn the Rovo Dev in Jira feature off at the organization and site level at any time.
この内容はお役に立ちましたか?