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

# Jira

> Prepare issue drafts and reviewed updates with project permissions, precise targets, and duplicate prevention.

Plan a Jira action that turns a reviewed support problem into an issue draft. The reviewer should see the project, issue type, summary, description, and selected fields before creation.

<Note>
  Jira is absent from the current native catalog. This page prepares an external integration; it does not provide an installation wizard or working issue-creation tool.
</Note>

## Prepare an issue workflow

You need a project owner, an approved test project, and a mapping between the proposed action and that project's required fields.

<Steps>
  <Step title="Review application authorization" id="jira-authorization">
    Atlassian's [REST authentication guidance](https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/) recommends OAuth 2.0 authorization-code grants for integrations. Do not build a distributed integration that collects customers' API tokens or asks each customer to create an individual OAuth app. Review the app's permissions and the user's project access together.
  </Step>

  <Step title="Prepare a concrete issue draft" id="jira-issue-draft">
    Include only the problem details needed by the project. Remove secrets and unnecessary customer data from transcripts. Resolve project and issue identifiers explicitly; names alone may be ambiguous. Validate required fields against the target project's current configuration.
  </Step>

  <Step title="Confirm writes and reconcile failures" id="jira-write-review">
    Review issue creation separately from comments, assignments, and workflow transitions. On an uncertain creation result, search for the intended issue before retrying. If the project rejects a field or transition, report that rejection without claiming the issue changed.
  </Step>
</Steps>

Document each action through [tool configuration](/agents-platform/configure/tools/overview). An [auth connection](/agents-platform/configure/authentication/auth-connections) cannot supply the missing interactive OAuth flow or release agent execution.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does a valid token grant every project permission?" id="faq-jira-project-permissions">No. The underlying user and project permissions still matter. Verify access to the actual project and operation.</Accordion>
  <Accordion title="Can a prompt choose any issue transition?" id="faq-jira-transition">No. The integration must validate transitions against the issue's current workflow and enforce authorization before requesting a change.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.