Bugs

Overview

This user guide offers step-by-step directions for reporting a bug found in a new release within a Client environment or adding an existing ticket to a specific release.

Bugs can be bugs, or they can be features, depending on the context and intention of both the user and the developer. Identifying "is this bug a bug" can be a challenge, and usually requires multiple parties to triage.

The process below defines the steps involved in identifying, triaging, and solving a bug.

Lucid Link

The lifecycle of a bug ticket is as follows:

1. Identify bug symptoms (an error message, a glitch, weird UI behavior, etc).
   1. Bug finder may wish to work with QA and engineering parties to verify that this is a bug vs an intended behavior/feature.
2. From the Empower Ticketing Dashboard, fill out a bug submission. The automation of that will:
   1. Alert our engineering and product leadership in a teams channel.
   2. Creates an Azure DevOps ticket on the Empower project.
3. Product and Engineering leadership then prioritize the bug based on its user impact and assign it to a pod lead for diagnosis.
   1. If the wrong pod lead was selected, this may be reassigned to another pod lead to act as Point.
4. Pod Lead confirms this bug and delegates the work within the pod according to prioritization.
5. Developer performs the fix according to priorities and updates the ticket (including whether this bug is a hotfix or not).
6. QA retests this ticket to verify bugfix. If not, then this goes back to the developer for fixing.
7. Product communicates the bugfix in the release notes.

To Report a Bug

1. Open theEmpower Ticketing Dashboard: This dashboard will automatically load once you click the tab. You may also navigate to this ticketing dashboard directly in Azure Dev Ops using the link above.
2. Click "Submit a bug": Enter details to the best of your ability. Keep in mind that you should fill in your contact information as well.
   1. Update the bug title: Provide information about the Release Version, Client, and include a brief bug title in the form RELEASE VERSION : CLIENT ]. . Examples: .20 : Lippert]****, .20 : All]
   2. Update the corresponding Release Target field to match the release the ticket is being hotfixed into.
   3. Add details to the bug: Describe the steps to reproduce the issue, include error details, and attach any relevant files, such as screen recordings, logs, or screenshots.
   4. Add system information: Fill in the system info section where necessary.
   5. If this bug was found in the pre-prod deployment (Capax) or in a client deployment (any customer), add the tag "Hotfix Request" to the ticket.
   6. Save the form: Your bug report will be submitted for review by the Product Managers.
3. Using Microsoft Teams, navigate to the Empower Releases Channel: In Microsoft Teams, locate the "Empower Releases" Channel. When you save your ticket from the step before, make sure to post your ticket here to alert the channel. There is automation to find these tickets as well, but immediate communication and followup is recommended for best turnaround time.