Issues to apply severity and priority for Quality
Hi @meks,
Here is a list of bugs without severity and priority for the team.
We would like to ask you to:
Work with your team to triage and add a severity label (~S1 / ~S2 / ~S3 / ~S4) and a priority label (~P1 / ~P2 / ~P3 / ~P4) to the issues in this list.
The definition of these labels are defined at:
For the issues triaged please check off the box in front of the given issue.
Please work with your team to complete the list this week.
-
Danger checks for Danger implementation changes Quality, ~"feature proposal" -
QA: Clarify the relationship between resources, products, and dependencies Quality -
QA: Separate tests for creating groups and projects QA, Quality -
~~Failing create tests in the pipeline ~"P1", Quality, ~"bug"~~ -
Improve validation of active/selected state of elements QA, Quality, ~"backstage" -
Create E2E/Integration tests for PlantUML Integration ~"Plan", Quality -
Test case management and test tracking in a Native Continuous Delivery way. Quality -
Find a way to figure out we want to GET or POST for QA resource QA, Quality, ~"backstage", ~"technical debt" -
Generating of merge request (diff) comments based on output of CI builds ~"CI/CD", ~"Framework", Quality, ~"feature proposal" -
Issues to apply severity and priority for Quality Quality, ~"triage-package"
Edited by Mek Stittri