Qualio Design Controls is used by companies creating medical device software to structure, strengthen and centralize their software development and quality activities.

This integration will require a Jira Administrator to:


Create an API Token

Create an API token from your Atlassian account. We highly recommend creating or using a service user that belongs to a group, rather than an individual. This will prevent connectivity issues if an individual leaves.

  1. Log in to https://id.atlassian.com/manage/api-tokens

  2. Click Create API token.

  3. From the dialog that appears, enter a memorable and concise Label for your token and click Create.

  4. Click Copy to clipboard, then past the token to your script, or elsewhere to save.

Please note, for security reasons it isn’t possible to view the token after closing the creation dialog; if necessary, create a new token. You should store the token securely, just as you would for any password.

Next, you will need to securely share the following with Qualio:

  • The API token

  • The email address associated with the account that created the API token

  • The host (e.g. qualio-product-sandbox.atlassian.net)

  • The Project Key (e.g. DC)

Create Issue Types and Add to Project

Next, you will create two issue types in JIRA: Test Case and Test Evidence. This step can be skipped if you are doing Test case and Test Evidence outside of JIRA. We currently support X-Ray and Testrails for test management integrations.

  1. Browse to the JIRA Settings menu and select Issues.

  2. Click the Add Issue Type button. In the modal, enter the name “Test Case” and select “Standard Issue Type”. The Description field is optional. Then click the Add button to proceed.

  3. Add another Issue Type for Test Evidence. Click the Add Issue Type button. In the modal, enter the name “Test Evidence” and select the “Sub-Type Issue Type”.

  4. Add Issue Types to Project from the Issue Types Schemes screen.

  5. Find the project you want to add the Issue Types to, and click on Edit.

  6. Modify the issue type scheme for the project by dragging the issue types Test Case and Test Evidence from the Available Issue Types to the Current Scheme panel, then click Save.

Create a Custom Field for Test Evidence Status

Each test evidence item will need to have a Passed or Failed status applied. Therefore, a custom field in JIRA will need to be created to support this motion.

  1. In the Settings Issues screen, go to Custom Fields, found on the navigation left-side panel.

  2. Click on Create custom field button.

  3. In the modal presented, choose ‘Select List (single choice)’ option, then click Next.

  4. Enter the name “Test Status”. Then add two options: Passed and Failed. The description field is optional. Then click Create.

JIRA Field Mappings

Part of the JIRA integration is to map relevant fields on Epics, Stories, Sub-Tasks, Test Cases, and Test Evidences to Design Controls fields.

JIRA Field

Design Control Field

Summary

Title

Description

Description

Status

Status

Key (e.g. JSP-1)

Code

Test Status (Test Evidence only)

Status

Next Steps

Now that configuration of Design Controls with Jira integration is complete, you can now begin creating requirements in Jira.

Did this answer your question?