This article follows the official documentation. We haven’t tested this tool for a hands-on review.
When a coding agent can run commands in a terminal, it can use the Atlassian CLI (acli) to search Jira. Jira is Atlassian’s service for tracking work, including tasks and bugs. Before changing code, the agent can check Jira work items for requirements.
acli includes commands for Jira work items, boards, projects, and sprints, including searches written in JQL. JQL, or Jira Query Language, is text for filtering Jira work items. When the CLI runs a Jira command, it sends a request to Atlassian and searches current data on the user’s Jira site, not data in the local repository.
This example uses the Jira commands to fetch requirements for an existing coding agent. The separate rovodev commands start Atlassian’s own coding agent.
Install and authenticate
On macOS with Homebrew, follow Atlassian’s installation instructions:
brew tap atlassian/homebrew-acli
brew install acli
acli --version
Atlassian also provides Linux packages and binaries and Windows instructions. Install the CLI before handing the task to your agent.
For Jira, you can sign in through your browser:
acli jira auth login --web
acli jira auth status
Choose your Jira site in the browser, accept access, then select the same site in the terminal. The CLI uses your account’s access to Jira. You do not need to paste a token into the agent prompt.
Search Jira from the terminal
The agent can start by finding recently updated work items for the project tied to the code it is changing. Replace YOUR_PROJECT_KEY with the project’s actual key, such as the short identifier in its Jira work item keys.
acli jira workitem search --jql 'project = YOUR_PROJECT_KEY ORDER BY updated DESC' --limit 20 --fields 'key,summary' --json
The query limits results to one project and sorts them by most recent update. --limit 20 keeps the response small. --fields selects the work item keys and summaries; --json makes the output easier for an agent or script to read. Atlassian documents these flags in the search command reference.
The CLI sends this request to your Jira site. It does not search a local copy of your tickets. If Jira rejects the request, check the account shown by acli jira auth status and whether that account can open the project.
The search command only retrieves work items; it does not change them. The agent can use the results to find the relevant requirement, then inspect the related files in the local repository. For example, give the agent this prompt:
Search Jira project
YOUR_PROJECT_KEYfor recently updated work items. Summarize the items relevant to the bug I’m investigating, then inspect the local repository for related code. Do not change Jira records.
The project key is a placeholder, not a public example key. The agent needs access to that Jira project, and the local repository must already be in its working directory.