> ## 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.

# Usage

> Bring Neo into a Jira issue with @neo, ask it to investigate and act on the work, attach files, and read Confluence for context.

Once your site is connected, you can use Neo with Jira in two ways: mention `@neo` on an issue from inside Jira, or ask Neo to work with your Jira issues from a Neo task.

## From Jira: mention `@neo`

Add a comment mentioning **`@neo`** (you can also use `/neo`) on the issue you want Neo to work on. Neo reads the issue and its context, does the work, and replies in the same issue as the bot.

Plain comments without `@neo` are ignored.

## What Neo can do

* **Read and investigate** the issue, its comments, and attachments
* **Retest a finding** to confirm whether a reported vulnerability is fixed
* **Update** the description, labels, priority, due date, and assignee
* **Move** the issue through your workflow
* **Create issues**, including turning a Neo finding into a linked ticket
* **Read Confluence** to search and read pages for context (when Confluence is connected)

<Note>
  **Confluence is read-only.** Neo can read and search Confluence, but can't create or edit pages. Reading Confluence also requires the Confluence connection. See [Install & Connect](/integrations/jira-install-and-connect).
</Note>

## Example prompts

* "@neo summarize this issue and the discussion so far."
* "@neo investigate this finding and tell me the likely impact and what to check next."
* "@neo retest this vulnerability and confirm whether the fix resolved it."
* "@neo set the priority to High and move this to In Progress."
* "@neo create a follow-up issue for the fix and link it here."
* "@neo read the linked Confluence design doc and tell me if this change adds risk."

## Attachments and files

Neo can read files attached to the issue or comment it's working on, such as logs, scanner output, reports, or code snippets, and use them in the task. When a comment points to a newly attached file, Neo reads the most recent one.

## What replies look like

* a short summary comment with the key outcome
* an **Open in Neo** link to the full details, evidence, and artifacts
* posted by the Neo bot, so it's clearly labeled

## Thread continuity

Each issue maps to one Neo conversation. A follow-up `@neo` comment on the same issue continues that thread, and Neo remembers what it already did.

When work outgrows a comment thread, open the task in Neo for the complete trail and longer follow-up.

## From a Neo task

You don't have to start inside Jira. In any Neo task, once Jira is connected, just ask Neo to work with your Jira issues and it uses the connection on your behalf. It can do the same things it does from a mention: read and search issues, create and update them, move them through your workflow, add comments, and read Confluence for context (when Confluence is connected).

Example prompts from a Neo task:

* "Find open high-priority security issues in the SEC project and summarize them."
* "Retest SEC-142 and confirm whether the reported vulnerability is fixed."
* "Create a Jira issue in SEC for this finding and set the priority to High."
* "Update SEC-142 with a remediation summary and move it to In Review."
* "Check the linked Confluence runbook and tell me if this matches our process."

## Next

* Setup and reconnect behavior: [Install & Connect](/integrations/jira-install-and-connect)
* Admin controls and permissions: [Admin & Permissions](/integrations/jira-admin-and-permissions)
* Fix common issues: [Troubleshooting](/integrations/jira-troubleshooting)