Jira: Search, Create, and Transition Issues

Search Jira issues with JQL, create and update them, comment, and move them through workflows. Connect in one click with OAuth.

Overview

OneCLI connects AI agents to Jira Cloud. Agents can search issues with JQL, read and create them, comment, and move them through a workflow. The gateway injects the token into requests to api.atlassian.com, so your agent never sees it.

Connecting takes one click. You don’t create an Atlassian app or copy any keys.

Connect Jira

1. Click Connect

   In the OneCLI dashboard, open Connections > Jira and click Connect Jira.

   

   The Jira connect window in OneCLI.

2. Accept in Atlassian

   Sign in to Atlassian, pick your Jira site, and click Accept. You’re done. OneCLI keeps the connection active from then on.

You don’t need to be a Jira admin. Atlassian may show a notice that the app hasn’t been reviewed by Atlassian yet. It’s safe to continue.

What agents can do

Tool	Description
Search issues	Find issues with JQL
Get issue	Read an issue and its sub-resources
List projects / Get project	List projects in the site, or read one
Create issue / Update issue	Open a new issue, or change its fields
Add comment	Comment on an issue
Transition issue	Move an issue through its workflow
Assign issue	Assign an issue to a user
Delete issue	Delete an issue

Controlling access

Grant the connection to each agent that needs it, and choose per tool what runs freely, what needs approval, and what’s blocked. For example, let an agent search and read freely, but put Transition issue and Delete issue behind approval. Organization rules add guardrails on top. A blocked request never reaches Jira.

To disconnect, remove the connection in Connections > Jira, then revoke OneCLI in Atlassian under Account settings > Connected apps.

---

Self-hosted: use your own Atlassian app

Skip this section on OneCLI Cloud. It’s only for self-hosted OneCLI without ATLASSIAN_CLIENT_ID and ATLASSIAN_CLIENT_SECRET set, or if you want your own company name on Atlassian’s consent screen. One Atlassian app serves both Jira and Confluence: you save it once, register one callback URL, and people connect either app with it.

1. Create the Atlassian app

Go to developer.atlassian.com/console/myapps. Select Create > OAuth 2.0 integration, name it OneCLI, accept the terms, and select Create. For Access type, choose Resource-level, so the token only reaches the site you pick.

2. Add the permissions

Open Permissions. For each API, click Add, then Configure:

API	Scopes
Jira API	read:jira-work, write:jira-work, read:jira-user
User identity API	read:me

Use these exact classic scope names. The granular ones (read:issue:jira and so on) don’t match what OneCLI requests.

Also add the Confluence scopes from the Confluence page, even if you only use Jira. Atlassian keeps one consent per person for each app, so OneCLI asks for the Jira and Confluence scopes together. If any of them is missing from the app, Atlassian shows an error instead of the consent screen.

Permissions after adding all four scopes.

3. Add the callback URL

In OneCLI, open Connections > Jira > Custom credentials and copy the Redirect URI. It ends in /v1/apps/oauth/atlassian/callback, the same URI for Jira and Confluence. In the developer console, open Authorization, click Configure next to OAuth 2.0 (3LO), paste it into Callback URLs, and save.

Copy the Redirect URI from Custom credentials in OneCLI.

4. Connect with your app

In the developer console, open Settings and copy the Client ID and Secret under Authentication details.

Client ID and Secret on the Settings page.

Paste both into Connections > Jira > Custom credentials, select Save & Connect, and accept in Atlassian. The app now serves Confluence too: connect it from Connections > Confluence without entering credentials again.

An Atlassian app has only one callback URL. If your app still has an older per-app URI (ending in /v1/apps/jira/callback), replace it with the one above.