Jira integration

Connecting Jira links one of your apps to a specific Jira site, project, and issue type. From then on, every report submitted from that app automatically creates an issue of that type in that project, with the description, screenshots, and classification. You authorize through Atlassian's OAuth screen.

You can connect more than one tracker to the same app; each report fans out to every connected integration independently.

• You've created an app in the BugScreen console.
• You can sign in to an Atlassian account with permission to create issues in the target project.

1. Open your app in the console and go to the Integrations section.
2. Click Connect Jira. You'll be redirected to Atlassian to authorize BugScreen.
3. Approve the authorization. You'll be returned to the console.
4. Pick the site, then the project, then the issue type new reports should use, and confirm.

Each report creates a Jira issue of your chosen type containing:

• A summary derived from the report and a formatted description.
• Screenshots and the captured log file uploaded as attachments on the issue.
• A "Reporter Classification" block in the description.

Priority & labels

• Severity maps to the standard priority field by name — Low, Medium, or High.
• Type is added as a label: bugscreen-type-bug, bugscreen-type-ui, or bugscreen-type-crash.
• The issue type you picked at connect time is always used and never overridden.

After connecting, use Test on the integration to confirm everything works end to end. The test files a real sample issue and shows you whether it succeeded.

To file into a different site, project, or issue type, disconnect the Jira integration and connect again with the new destination. One integration maps to one project — connect Jira again if you want reports in more than one project. Disconnecting stops issue creation for that app.

If a test or real report fails to create an issue, check the following:

• The authorized account lost access to the project. Reconnect with an account that can create issues there.
• A required field blocks creation. If the project requires custom fields on the create screen, the issue may be rejected — relax those requirements or use a simpler issue type.
• Priority or labels don't appear. They're hidden on the create screen; the classification is still in the description.
• Connect is blocked with a plan-limit message. Your plan's integration limit has been reached — remove an unused integration or upgrade your plan.