Connect Jira

Tickets file into a Jira Cloud project you choose. Connecting takes about two minutes and needs a Jira user who can access the target project.

1. Start the connection

In the app: Settings → Integrations → Jira → Connect. You'll be sent to Atlassian to approve access for your Jira site.

Jira connect card

2. Approve in Atlassian

Approve the requested access and pick the site if you have several. You land back in Settings with the connection marked active.

3. Pick a project and issue type

Choose the project tickets should land in and the issue type (most teams use Task or Bug). Both dropdowns are live from your Jira — if a project is missing, the connected Jira user can't see it.

4. Test it

Use the Test button on the card. It files a clearly-labeled test issue through the exact same pipeline as real tickets and shows you the link. Safe to close in Jira immediately.

What ends up in Jira

Each ticket carries a summary, the plain-English diagnosis, the exact Salesforce component behind the error, the user's last steps (labels only — never what they typed), and the masked screenshot if one was attached.

For your IT team

OAuth 2.0 (3LO) against Jira Cloud; tokens are encrypted at rest and can be revoked in Atlassian admin at any time.
Failure codes surfaced on tickets: DESTINATION_AUTH (reconnect needed), DESTINATION_INVALID_CONFIG (project/type no longer valid), DESTINATION_REJECTED (Jira refused the payload — usually a required custom field on the issue type).
Fix for required-custom-field rejections: use an issue type without extra required fields, or default them in Jira.

Trouble? See Troubleshooting or email hello@rootcase.io.

Regenerating the screenshots on this page (maintainers)

jira-connect.svg — staging Settings → Integrations with the Jira card in the disconnected state; capture card only. After OAuth against the sandbox Jira, re-capture for the connected state if we add that image.

Was this helpful?