> ## Documentation Index
> Fetch the complete documentation index at: https://onecli.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira Integration: Issues, Sprints & Project Boards

> Create, update, and search Jira issues. Agents can manage sprints, transition statuses, and read project boards.

## Overview

OneCLI connects AI agents to Jira through Atlassian's OAuth flow. Agents can search for issues, create new tickets, update fields, and manage sprints. The gateway injects OAuth credentials into requests to the Jira REST API automatically.

This is useful for coding agents that need to look up ticket details, create sub-tasks, update issue status after completing work, or report bugs.

## Setup

<Steps>
  <Step title="Go to Connections">
    Open the OneCLI dashboard and navigate to **Connections** > **Jira**.
  </Step>

  <Step title="Authorize">
    Click **Connect Jira**. You'll be redirected to Atlassian to authorize OneCLI. Select the Jira site to connect and click **Accept**.
  </Step>
</Steps>

## What agents can do

* Search issues using JQL (Jira Query Language) with filters for project, status, assignee, labels, and more
* Read full issue details (summary, description, comments, attachments, custom fields)
* Create new issues with specified project, type, summary, description, and fields
* Update issue fields (status, assignee, priority, labels, custom fields)
* Add comments to issues
* Transition issues between statuses (e.g., move from "To Do" to "In Progress")
* List projects and their issue types
* Read and manage sprint boards (list sprints, get sprint issues)
* Create and update epics
* Link related issues together
* Log work time against an issue

## Controlling access

Access is per agent: [grant](/docs/guides/agent-access) the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization [rules](/docs/guides/rules) add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Jira.