-
Notifications
You must be signed in to change notification settings - Fork 21
defectmgmt
Any Health Gateway team member may create a bug within the Azure DevOps instance. Prior to creating a bug, the team member should search Azure DevOps for duplicates or similar issues.
Every bug should contain:
- The identified issue with as much detail as possible.
- The perceived severity of the ticket with justification.
The defect should be left unassigned and should be put into the current Sprint for review.
Once a bug has been created in Azure DevOps, the Health Gateway Product Owner will review the bug, validate uniqueness and bring it to the team grooming ceremony for triage.
During triage, the bug will have its severity verified, its priority assessed, and an estimate added. The bug will either be left in the Sprint for
- Immediate work if the Severity/Priority warrant it
- Potential Sprint work once committed work is delivered
or it will be moved to the backlog for later planning.
-
Developer Standard and Processes
-
Workstation Setup
-
IDE Configuration
-
Application Config
-
RedHat SSO Authorization Server
-
Known Issues