Work with Jira Coding Agent in automations
Use Jira Coding Agent in automations to automatically generate code for repetitive tasks at scale so your team can focus on high valuable work.
How Jira Coding Agent works in automations
An automation flow for Jira Coding Agent uses the standard building blocks of Jira automation:
A trigger to kick off the execution of your flow, for example when a work item is updated.
Conditions to narrow the scope of your flow, for example when a specific label is added to the work item.
An action to perform the task you want to automate. With Use Jira Coding Agent action you can add other follow-up actions too.
When a Jira work item meets your flow conditions, the automation runs. The Use Jira Coding Agent action connects the Jira Coding Agent to a repository so it can make code changes and open a pull request. It doesn’t merge the pull request directly, but hands it back to your team for review and merge.
Find out how Jira Cloud Automation works in general
The Jira Coding Agent runs in a restricted mode in automations and doesn’t use Atlassian Teamwork Graph context. This means that the Jira Coding Agent won’t read Confluence content that the session owner has access to.
Automation flows using the Jira Coding Agent will count towards automation limits of your Jira plan.
Read about Jira plans and pricing
Before you begin
To create and manage automation flows using the Jira Coding Agent, make sure:
You’re a space admin for the Jira space where you want to create automation flows. Permissions required to manage automation flows
The Jira Coding Agent is available on your site and you can access it.
You’re on a Standard or Premium plan.
You have Rovo credits available. How Rovo credits work
You must be a Jira space admin to create and manage space automation flows. However, any Jira user can trigger those flows, either manually or when a work item meets the flow’s conditions.
You can choose who owns the sessions generated by the Use Jira Coding Agent action:
Connection owner: the owner of the action’s connection. Use this for flows that don’t run on a work item, such as scheduled flows. Understand connections in automation
User who triggered the rule: the person whose action started the flow, for example by creating or updating a work item, or by triggering it manually.
Work item assignee: the person assigned to the work item the flow runs on.
Create an automation flow to generate code
Define your common coding patterns and use the Jira Coding Agent to automatically generate code for repetitive tasks.
Start by automating small, low-risk tasks with the Jira Coding Agent automation action. As you get comfortable, expand to more scenarios and complex tasks.
To create an automation flow to generate code:
In your Jira space, select More actions () next to your space name, then select Space settings.
In the sidebar, select Automation.
Select Create flow.
Under Add a trigger, select a trigger, set it up, then select Next.
Select Add step, then Add an action.
Under Add an action, search for and select Use Jira Coding Agent.
Select a connected repository from the list, or select Infer repository from work item if you will add repository details to your work item descriptions.
Select Settings () to configure the branch name and source branch, and whether to create a pull request after each automation. If you create a pull request, choose whether it’s a draft or ready for review.
In the Custom instructions field, give the Jira Coding Agent instructions on the code you want to generate.
Optionally, select a model for the Jira Coding Agent to use.
Under Session owner, choose who owns the sessions this flow creates: connection owner, user who triggered the rule, or work item assignee.
Select Next.
Select Turn on flow.
Things to keep in mind
To see when a flow was triggered and code was generated, view the audit log
The time required for the flow to run depends on repository size and complexity of the task.
The session owner’s Rovo credits are used when the flow runs.
If the selected session owner isn’t available, for example a work item has no assignee, the flow fails and no session is created. Check the audit log for error details.
When the flow runs, the Jira Coding Agent makes code changes on a branch and creates a pull request in the repository you provided. You can review the pull request directly in the repository, or open the Jira work item and use the repository link under:
the Development section in the Details panel
the Agent sessions section
The Agent sessions section displays all agentic sessions related to that work item, including sessions owned and managed by other users.
Find the Jira Coding Agent for sessions you own to review the changes, make any edits you need, then approve and merge the pull request when you’re ready.
Use smart values
Smart values change the behaviour of flows based on specific criteria. Understand smart values in automation
This means smart values can be used in the repository and custom instructions fields of the Use Jira Coding Agent action.
For example, using the {{issue.labels}} smart value, you could get the Jira Coding Agent to code in one repository or another based on the work item label.
The Use Jira Coding Agent action also outputs smart values to use in other automation steps:
Smart value | Description |
|---|---|
| ID of the coding session |
| URL of the repository |
Consider how you might use templates for Jira Coding Agent automations
Was this helpful?