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

# Overview

> Bring Neo into Jira and Confluence. Mention @neo on an issue, or ask Neo from a task, to triage, investigate, update, and act on the work.

Neo works right inside the tools your team already uses. Mention `@neo` on a Jira issue and Neo will investigate it, summarize it, update or move it, create linked issues, and pull in context from your Confluence pages, all without leaving Atlassian.

Neo installs as a **native Atlassian app** and runs as a **bot**. It doesn't take up a Jira seat or license. You simply bring it into an issue by mentioning it.

## Two ways to use Neo

Once connected, you can use Neo with Jira from either side:

* **From Jira**: mention `@neo` on an issue, and Neo replies right in the issue.
* **From Neo**: in a Neo task, ask Neo to work with your Jira issues and Confluence pages, and it uses the connection to read and act on them.

## Connecting Jira and Confluence

Neo connects to **Jira** and **Confluence** as two independent connections. You set each one up on its own in **Settings → Applications**.

* Connect **Jira** to let Neo read and act on issues.
* Connect **Confluence** to let Neo read and search your pages for context.
* Connect **one or both**. They don't depend on each other.

<Note>
  **Confluence is read-only.** Neo can read and search Confluence pages, but it never creates or edits them.
</Note>

## What you can do

Mention `@neo` on an issue and Neo does the work, then posts a short reply as the bot. You can ask it to:

* **Investigate and summarize** an issue, its comments, and attachments
* **Update issues** such as the description, labels, priority, due date, and assignee
* **Move issues** through your workflow (for example, *In Progress* to *Done*)
* **Create issues**, including turning a Neo security finding into a linked ticket
* **Read Confluence** for related context (when Confluence is connected)

## How replies work

Neo keeps Jira readable. It posts a short comment with the key outcome plus an **Open in Neo** link to the full details and evidence. Replies come from the Neo bot, so they're clearly labeled.

Each issue maps to one Neo conversation. Follow-up `@neo` comments on the same issue continue that thread without you re-explaining anything.

## Who sets it up vs who uses it

* **Atlassian site admin**: installs the Neo app on your Jira and Confluence site.
* **Neo team admin**: connects and manages Jira and Confluence from Neo's Applications settings.
* **Everyone else**: mentions `@neo` on issues once a site is connected.

## Next steps

<CardGroup cols={2}>
  <Card title="Install & Connect" icon="plug" href="/integrations/jira-install-and-connect">
    Connect Jira and Confluence, and manage reconnect, disconnect, and switching sites.
  </Card>

  <Card title="Use Neo In Jira" icon="messages" href="/integrations/jira-use-neo-in-jira">
    Learn how `@neo` mentions, issue actions, attachments, and Confluence reads work day to day.
  </Card>

  <Card title="Admin & Permissions" icon="shield" href="/integrations/jira-admin-and-permissions">
    Review the permissions Neo requests and how admins manage the connection.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/integrations/jira-troubleshooting">
    Fix connection states, awaiting-install, and site-switching issues.
  </Card>
</CardGroup>

<Card title="Privacy & Support" icon="life-ring" href="/integrations/jira-privacy-and-support">
  Review how Neo handles your Jira and Confluence data, plus support and trust resources.
</Card>