Create an issue

This document details how an incident should be prepared, giving the necessary data for its reproduction. This will be a very necessary tool to be able to reproduce this incidence in other environments (DEV and/or QA).

Bug reporting structure

  1. Title: summary
    1. eg: Wrong message when registering a user.
  2. Body:
    • Preconditions: Environment, URLs, credentials, data and necessary actions prior to the execution of the steps.
    • Steps: List of instructions for the reproduction of the incident.
    • Result obtained: Description of the behavior of the system.
    • Expected result: Description of the expected behavior of the system.
    • Notes / clarifications.
    • Attached files: screenshots, videos, logs.
  3. Classification / Criticality
    • Blocker: Prevents the user from accessing or using a fundamental feature of the system. It causes loss of information. Represents an integrity risk to user information. Violate security.
    • Critical: Makes it difficult to use a system feature, without preventing it completely.
    • Major: Corresponds to new functionality. Makes it difficult to use a system feature.
    • Minor: Does not affect functionality. Includes proposed improvements.
    • Trivial: look & feel, design.