3.7 QA Release & Bug Triage status

This page contains all bugs reported for 3.7 release for tracking and status. This page will be used during daily bug triage, and queries must be updated with labels of 3.7Phase1bug or 3.7Phase2bug.

Bug Triage team

Members	Responsibilities	Notes
Joanna Bebak (Deactivated) Joanna Szymańska (Deactivated) Sebastian Brudziński Wesley Brown Douglas Khumalo (Unlicensed) - Malawi	Review list of bugs provided by Joanna Bebak (Deactivated) in QA slack channel (see query below) Only bugs that have been entered and labeled 3.7Phase1bug or 3.7Phase2bug will be reviewed during triage Prioritize bugs Communicate which bugs need to be fixed, who is assigned to fix for each team - only bugs prioritized as Blocker or Critical must be fixed Joanna create test cycles for retesting if needed Joanna provide status update on bug fixes in QA slack channel as needed Joanna communicate in Slack the bugs that have been added to the board for the day.	Meet every weekday once in the morning (6 AM PST) and a communication on bug triage status at the end of the day Guidance on Bug prioritization is located here: http://docs.openlmis.org/en/latest/contribute/contributionGuide.html#reporting-bugs If there are bugs found, then we must retest (see workflow diagram for testing after bug fix phase) Communication of the test plan before we start testing for the release Joanna Bebak (Deactivated) is responsible for communicating the test plan and bug status in the QA Slack channel

3.7 Phase 1 bugs

type	key	priority	summary	status	assignee	fixversions	created	updated	issuelinks	labels

Loading...

Refresh

3.7 Phase 2 bugs

type	key	priority	summary	status	assignee	fixversions	created	updated	issuelinks	labels

Loading...

Refresh

OpenLMIS

3.7 QA Release & Bug Triage status

Analytics

Bug Triage team

3.7 Phase 1 bugs

3.7 Phase 2 bugs

Related content