--- title: "Jira integration for design controls | Qualio" canonical: "https://www.qualio.com/integrations/jira" updatedDate: "2026-11-02T11:44:43.000Z" description: "Design controls built from the Jira project you already run. Qualio reads issues, links, parents and subtasks as they are, every hour, and writes nothing back. No plugin, nothing changes in Jira." --- # Jira integration for design controls | Qualio Design controls built from the Jira project you already run. Qualio reads issues, links, parents and subtasks as they are, every hour, and writes nothing back. No plugin, nothing changes in Jira. ## Design controls built from the Jira projects you already run Qualio reads the issues, links, parents and subtasks of the project you choose, as they are, and writes nothing back to Jira. ## What Qualio reads from Jira Qualio reads the issues in the project you choose: every standard and custom field, the description as Jira renders it, the issue links, parent and subtasks. Each link becomes a trace link, and each element keeps its issue key and a link back to Jira. ## Connect Jira in three steps - Connect Jira Cloud with your site URL, an email and an Atlassian API token. - Choose the project, the issue types that are requirements or tests, and a rule for anything narrower. - Preview, save, and Qualio reads at once, then every hour. ## What you get #### The traceability matrix rebuilds itself on every change Qualio links each test to its requirement and each risk to the element it controls. Before the review, an amber mark shows any requirement with no test. #### Your engineers stay in Jira, and the design controls keep up Each change to a ticket reaches its element on the next read. The element carries Qualio's own control status, and shows the Jira status beside it only if you map it as a field. #### Approve the design review and the documentation generates itself Approvers sign electronically. On approval Qualio generates the trace matrix, risk file, specifications and test plans, then exports them with test evidence and change history. #### A bug or a service desk ticket becomes a quality event Connect your Jira Service Management or bug project, with a rule on issue type, status or a label. Qualio raises each matching ticket as a complaint or nonconformance, with the ticket linked. Engineering keeps the bug and quality gets the event. ## Where it stops Comments and attachments stay in Jira. Qualio reads the issue, not the conversation around it. It writes nothing to Jira. #### If the token expires If the token expires, Qualio marks the connection Disconnected at once and pauses reads, with a banner on the Integrations page until you reconnect. #### Delete an issue Delete an issue and its element is marked deleted within about six hours; removing it from the design controls is an approval in Qualio. ## Guides ## Questions about the Jira integration ### Does our Jira project have to change? No. You choose the project, the issue types and a rule for what counts, one label at its simplest, with no JQL to write. Then you tell Qualio which requirement or test level each type is. Your issue keys stay on the elements as their codes, or Qualio issues its own, whichever you choose when you set the connection up. Your workflows, custom fields and structure stay as they are. ### We run Xray or Zephyr Scale on top of Jira. Do we connect both? Yes. A test in Xray or Zephyr that references the Jira key is linked to that requirement in Qualio, so the trace crosses tools without anyone drawing it. Connect Jira first, then Xray or Zephyr Scale with its own API key or token. Requirements come from Jira, test cases and results from the test tool. The link between a test and the issue it covers becomes a trace link in Qualio. If Jira disconnects, the test tool pauses until it is back. ### How often does Qualio read Jira? The first read runs when you save the connection. After that Qualio reads the project every hour and picks up the issues that changed since the last read. A change to your rule applies on the next read: Qualio marks an issue that stops matching as deleted and brings in one that starts. There is nothing to schedule on your side. ### What access does it need, and what does it write back? An Atlassian API token for a user who can see the project, with the site URL and that user's email. Qualio uses the token to read and writes nothing with it. Revoke it in Atlassian and the connection stops the same hour, with nothing to uninstall on the Jira side. ### Who needs a seat? People who write or approve in Qualio pay: the product manager who signs a design review, the person who owns the procedures. An engineer who writes requirements and tests in Jira needs no seat, because Qualio reads them in and nobody edits them there. Everyone who reads or trains is free. ## What a Jira project becomes in Qualio See a Jira project read into Qualio on the demo: the issues as requirements, the links as trace links, nothing changed in Jira.