Integrate Jira with Qualio to connect your issue tracking and project management data. This integration enables you to:
Automatically sync Jira issues into Qualio.
Link issues to design controls, events, and other quality processes.
Improve traceability and collaboration between development and quality teams.
IMPORTANT: The following steps may require authentication, approval, or direct involvement from your Jira administrator in order to successfully set up and configure the connection. Speak with your administrator if you have any questions.
Supported Jira Deployments
The Qualio–Jira integration supports Jira Cloud only. The authentication flow uses Atlassian API tokens issued from id.atlassian.com, which is not available for self-hosted Jira Server or Jira Data Center instances.
Preparing to integrate Jira to Qualio
Create a dedicated Jira user for the integration
Before connecting, create a dedicated Jira user for the integration. Use a licensed Jira user that belongs to a group, with a clear purpose-indicating name - for example, service-user (service-user@yourcompany.com).
Do not use a personal or individual account, and do not use Atlassian's built-in system service account (the one labeled "service account by Jira"), which is not supported.
A dedicated Jira user that belongs to a group:
Prevents disruptions if a person leaves the company or their personal account is deactivated.
Gives you control over access, you can grant this user only the project and permission scopes Qualio needs.
Keeps audit trails clean, Jira activity created by the integration is clearly attributed to the integration, not to an individual.
Permissions this Jira user needs
Integration only reads from Jira - Qualio does not write back to your Jira instance.
Make sure the dedicated Jira user has the access needed to read issues, projects, and related metadata across every Jira project you want to sync with Qualio. In practice, this usually means adding the user to a group that already has the appropriate project role (for example, Developers) for each relevant project.
To sync all issue fields - particularly custom fields and any fields with field-level restrictions - the dedicated Jira user typically needs administrator access in Jira. Without admin-level access, some fields may not be readable by the integration and will appear empty or missing in Qualio.
Create a Jira API Token
The dedicated Jira user authenticates to Qualio using an Atlassian API token. Log in as that Jira user (not your personal account) before completing these steps.
Log in to https://id.atlassian.com/manage/api-tokens as the dedicated Jira user.
Click Create API token.
In the dialog, enter a memorable and concise Label for the token (for example, Qualio integration Token).
Set an expiry date for the token. Atlassian requires every API token to have an expiry (up to one year).
Choose the longest period your organization's security policy allows, and note the expiry date so you can rotate the token before it expires.Click Create.
Click Copy to clipboard, then paste the token somewhere secure, so you can use it in the next section.
Note: For security reasons, the token cannot be viewed again after you close the creation dialog. Store it securely, just as you would any password. If you lose it, create a new token and revoke the old one.
Set up the Jira integration in Qualio
Navigate to Integrations & Imports: Go to Settings > Integrations & Imports.
Connect to Jira: Click Connect on the Jira tile.
Enter the following on the integration page:
Jira Workspace URL (for example, https://your-company.atlassian.net).
Email address of the dedicated Jira user you created above.
API token from the previous section.
Click Connect. Jira will appear under Your integrations on the Integrations tab.
Troubleshooting
If the connection fails or issues aren't syncing as expected, work through the checks below before contacting our Support Team.
"Invalid credentials" or "Authentication failed"
Confirm you're using the dedicated Jira user's email address, not a personal email, and that the email matches the Atlassian account that generated the token.
Re-generate the API token at https://id.atlassian.com/manage/api-tokens and paste it again. Tokens can be revoked by an Atlassian admin without notice.
Make sure there are no leading or trailing spaces when pasting the token or URL.
"Workspace URL is invalid"
Use the full Atlassian Cloud URL, including https:// (for example, https://your-company.atlassian.net). Do not include a trailing slash or a project key.
Confirm the instance is Jira Cloud. Server/Data Center URLs are not supported.
The integration stops working unexpectedly
Disruptions typically stem from modifications to the dedicated Jira user account, its permissions, or its API token. Verify the user remains active, retains its group assignments, and that its token has not expired or been revoked. If this occurs, a warning notification will be visible on the Integrations & Imports page.
If your Atlassian admin enforces token rotation, schedule a recurring reminder to rotate the Qualio token before it expires.
If you've worked through these checks and the issue persists, contact Qualio Support with: the workspace URL, the dedicated Jira user's email, the approximate time of failure, and a screenshot of any error message.
Creating Automated Workflows
Once you've set up the Jira integration, you can automate workflows within Qualio.
Learn more: Create Workflows with Integrations




