Skip to main content
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.
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.

​
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.
1

Review application authorization

Atlassian’s REST authentication guidance 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.
2

Prepare a concrete 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.
3

Confirm writes and reconcile failures

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.
Document each action through tool configuration. An auth connection cannot supply the missing interactive OAuth flow or release agent execution.

​
Frequently asked questions

No. The underlying user and project permissions still matter. Verify access to the actual project and operation.
No. The integration must validate transitions against the issue’s current workflow and enforce authorization before requesting a change.