Overview
This guide will help you know where and how to be report bugs to the engineering teams. For us to be able to understand the bug and explain the necessary work that needs to be done we need certain information in the service desks tickets.
Where to report bugs?
Please report them in the service desk found in this link (https://rbictg.atlassian.net/servicedesk/customer/portal/2) so we can track all the issues in a consistent matter
How to report bugs?
Please follow the next steps to add all information to bug ticket
Brand: Which brand and country are you reporting from?
Env: Which environment this happens in? Ideally, we catch bugs in development and staging environments but in some cases, there are some bugs in production. If it happens in multiple environments use the scale as the highest environment it is affecting in. The environment levels are: Prod, QA, Staging and Dev. So if there is a bug in QA, Staging and Dev just mark it as a QA bug
Summary: Please add relevant information for us to know what the bug is about. This is usually one sentence that describes the issue.
Attachment: Any pictures and videos that could be helpful for us to understand what the issue is.
Priority: We need to set priority for the bug for us to understand how much is affecting and the importance of it. The scale goes as:
Components: Select the category your issue belongs to. If you would need one added please let Patricia know (partiaga@rbi.com)
Description: This one is the most important of all as it will help us understand what the issue is. In the description we will need
Steps to reproduce: What steps do the users need to follow to find this bug. If there are multiple display the different routes the user should follow.
Current behaviour: Explain in detail what the issue is and why is it failing.
Expected behaviour: Explain what is the behaviour expected, what should happen if this bug wasn't there.
Link to the item/issue in Sanity or website