By syncing design elements from your product development software into Qualio, Quality Teams have visibility to current product development design elements.
‘Design elements’ is a catch-all term which refers to multiple levels of requirements and risks generated during the product development lifecycle. Managing these elements without Design Controls can be time consuming, tedious, and prone to human error. But with Design Controls, your design elements will be arranged logically by product, providing a visual traceability between different levels of requirements and testing.
This article is written for customers using a Jira to document requirements, have already worked with the Qualio Support team to set up the Jira integration, and are ready to sync design elements to Design Controls. This article describes the following:
Please note that because design requirements are created in your third party application, you will also need to modify requirements from your third party application. Also, because requirements are sourced from third party applications, attachments can not be added within Design Controls or transferred.
Additionally, this article assumes 3 levels of requirements, however, the setup is easily catered for your own number of levels that are not more than the supported 3 levels.
Create an Epic (Level 1 Requirement)
Open the chosen Project. Click on the Create button on the top of the screen.
A modal will open. In the Issue Type dropdown select “Epic”. Enter an Epic Name and Summary (title) of the epic. Description is optional. Then click Create.
To ensure traceability, when applicable, link the epic to a story (level 2 requirement) and/or test case(s) by clicking on the Link Issue button.
From the “relates to” dropdown, enter the story and/or test case code(s). Then click the Link button.
Create a Story (Level 2 Requirement)
Open the chosen Project. Click on the Create button on the top of the screen.
A modal will open. In the Issue Type dropdown select “Story”. Enter a Summary (title) for the story. Description is optional. Then click Create.
To ensure traceability, when applicable, link the story to a test case by clicking on the Link Issue button.
From the “relates to” dropdown, enter the test case code(s). Then click the Link button.
Create a Sub-Task (Level 3 Requirement)
Open the chosen Project then applicable story (level 2 requirement). Click on the Create Sub-Task button on the top of the screen.
From the dropdown, select “Sub-Task” and enter the name of the sub-task.
Once created, you can edit the sub-task description by clicking on the sub-task code.
Create a Test Case
Open the chosen Project. Click on the Create button on the top of the screen.
A modal will open. In the Issue Type dropdown select “Test Case”. Enter a Summary (title) for the test case. Description is optional. Then click Create.
Create Test Evidence
Open the chosen Project then the applicable test case you want to demonstrate test evidence for. Click on the Create Sub-Task button on the top of the screen.
From the dropdown, select “Test Evidence” and enter the name of the test evidence (e.g. The date it was run.)
Once created, edit the “Test Status” field by clicking on the test evidence code, then select “Passed” or “Failed” from the dropdown, based on what happened during the test run.
Viewing Requirements & Traceability in Design Controls
When Product Teams create requirements in a third party application, Quality Teams can view those requirements and confirm traceability in Design Controls by browsing to the Requirements tab and expanding the different levels of requirements.
The View More button, next to each requirement, will open a new tab and direct viewers to the third party application and synced issue or sub-task.
Next Steps
Once a few design requirements have been added, you may be ready to assess and log risks associated with the design requirements you created.