Jira Integration Guide
Connect Testably with Jira Cloud to streamline your bug tracking workflow. Create Jira issues directly from failed test results.
Starter Plan or Above Required
Jira integration is available on the Starter plan and above. View pricing to upgrade your team.
Prerequisites
Jira Cloud Account
You need an active Jira Cloud instance (e.g. yourcompany.atlassian.net). Jira Data Center / Server is not currently supported.
Create a Jira API Token
Go to id.atlassian.com → API Tokens and create a new token. Copy it immediately — it cannot be viewed again.
Setup
Connect your Jira Cloud instance to Testably in a few steps.
Open Integrations
In Testably, go to Settings → Integrations and click on the Jira card.
Enter Credentials
Fill in your Jira domain, account email, and the API token you created.
Select Default Issue Type
Choose the Jira issue type to use when creating issues from failed tests (e.g. Bug, Task, Story).
Test Connection
Click Test Connection to verify Testably can communicate with your Jira instance. You should see a success confirmation.
Save
Click Save to activate the integration. A green "Connected" badge will appear on the Jira card.
Usage: Create Jira Issues from Failed Tests
Once connected, you can create Jira issues directly from your test results.
Open a Test Run
Navigate to a completed or in-progress test run.
Find a Failed Result
Look for test cases with a failed status.
Click "Create Jira Issue"
A dialog will appear pre-filled with the test case title, steps, and failure details. Select the Jira project, adjust fields if needed, and submit.
Issue Created
The Jira issue key (e.g. PROJ-123) will be linked to the test result for easy reference.
Linked Jira issues appear in the test result detail view, so your team always has context on reported bugs.
Troubleshooting
Common issues and how to resolve them.
Connection test fails
- Verify your Jira domain is correct (e.g. yourcompany.atlassian.net)
- Check that the email matches your Atlassian account email
- Ensure the API token has not expired — regenerate if needed
- Confirm your network allows outbound HTTPS to Atlassian
Permission errors when creating issues
- The Jira user must have "Create Issues" permission in the target project
- Check that the project key exists and is accessible
- Verify the API token belongs to a user with project-level access
Issue type not appearing
- Only standard issue types are supported (Bug, Task, Story)
- Custom issue types may not appear — contact support if needed
- Ensure the issue type is available in the target Jira project scheme
Test Automation SDK Reporters
Testably provides native reporter plugins for the most popular test frameworks. After your test suite runs, the reporter automatically uploads results to a Testably run — no manual API calls needed.
Playwright
@testably.kr/playwright-reporterAuto-uploads results after playwright test completes.
Cypress
@testably.kr/cypress-reporterHooks into after:run to push results at the end of your Cypress suite.
Jest
@testably.kr/jest-reporterImplements onRunComplete to bulk upload Jest results.
# Playwright npm install --save-dev @testably.kr/playwright-reporter # Cypress npm install --save-dev @testably.kr/cypress-reporter # Jest (coming soon) # npm install --save-dev @testably.kr/jest-reporter