> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/connectors/jira/manual_creation.md).

# Manual Ticket Creation

You can create a ticket for an individual finding even when automatic ticketing is disabled. Open the finding in **Findings**, choose **Create ticket**, add an optional note, and confirm. The current dialog uses the connected ticketing destination and selects the project through configured routing; it does not expose a Jira-specific project/issue-type picker.

![Create ticket dialog with a sample finding](https://3946391995-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FId2OtLCL6O6V3XSRYxtr%2Fuploads%2Fgit-blob-fed1efe4820ffa56b79771efcf57e121d3ed1cf5%2Fcreate-ticket.png?alt=media)

After creation, follow the ticket link on the finding to inspect its destination, assignment, and content. A failed request is not a created ticket; check the error before retrying.

## Routing and prerequisites

Connect Jira and configure its default project and issue type first. [Ticketing settings](/configuration/configuration-ticketing.md) describe proposal routing and explicit API destinations. Manual ticket creation is distinct from an automatically approved ticket proposal and may require its own permissions. Check [assignee mapping](/connectors/jira/assignee.md) if the resulting issue has no owner.

Older dashboards place the action on a triage or vulnerability detail page. The API remains available for automation; use the finding type's `/ticket` operation in the [API reference](/api-reference/api-reference.md).
