Bug Description Template

DESCRIPTION

The “Description” field must be filled with all the following information:

Description	Brief bug description, given details that don’t fit at repro steps.
Platform/device	Web, App, OS, browser, screen resolution.
Environment	Indicate what/which environments the issue happens in order to help the developer reproduce and understand the issue.
Repro Steps	Description of how to reproduce the bug.
Current Behavior	Add the current result to make use the different between the expected behavior.
Expected Behavior	Description of what is expected behavior when the bug is corrected.
Data Used	Description of the data mass used when the bug was found.
Notes	This is a space to write complement information about the fixing or the bug itself.
Bug evidence	Can be a image, video or body response with the bug.

LABELS

The “Labels” field must be filled in with information below, in order to assist in analyzes related to continuous improvement.

Phase Label
Client Label
Origin Team Label

The information used to classify each bug for each category can be found below, using the “Label’s Code” to fulfill the Labels field.

Phase labels:

We must use this label in order to indicate which moment of the development the issue was found.

Phase	Description	Label’s Code

Phase	Description	Label’s Code
Development phase	For bugs found by development team (developers and QAs) while doing code review, unit tests or explore tests	PHASE_DEV
HML phase	For bugs found by development team or by client at homologation phase	PHASE_HML
Rollout	For bugs found by development team or by client at rollout phase	PHASE_PROD

Client label:

We must use this label in order to indicate who found the issue. We need only to use this label if the issue was found by the client. Commonly, the phases could be HML or Rollout on QA/STG/PROD enviroments.

Who?	Description	Label’s Code

Who?	Description	Label’s Code
Client	For bugs found by client.	FOUND_BY_CLIENT

Origin label:

We should use this label to indicate the team that generated this issue. However, we only need to use this label if the issue was generated by an external team or any other team other than our own.

Origin Team	Description	Label’s Code

Origin Team	Description	Label’s Code
External team	For bugs generated by an external team or any other team other than our own.	GENERATED_BY_OTHER_TEAM