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.
Please do not post about new or connected issues in Resolved tickets. For visibility and tracking, raise a new Bug ticket for each new issue. Messages posted in Resolved tickets may get overlooked due to insufficient notifications.
One ticket, one bug – don’t report multiple issues in one ticket. Rather, create separate tickets for each bug
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
Number of Impacted Users or Restaurants: Please add the number of impacted users and/or restaurants to determine the priority of the 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. Please don’t include any Personally Identifiable Information (PII) as an attachment. If you need to share any PII, contact your Customer Success Manager.
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 behavior: Explain in detail what the issue is and why is it failing.
Expected behavior: Explain what is the expected behavior, what should happen if this bug wasn't there. This is a key piece of information which will help our Tech Support team troubleshoot the issue
Link to the item/issue in Sanity or website
Priority: We need to set priority for bugs for us to understand how much functionality is affecting and the impact of it. The scale and corresponding Service Level Objectives are as follows:
Issue Priority | Definition | Time to First Response | Update Frequency | Resolution Time |
|---|---|---|---|---|
Fire | Impacting core functionality (offers, loyalty, ordering, sign-in) for a significant (>5%) number of users or otherwise bringing significant risk to the market (security breach, GDPR, etc) | 15min | Hourly | 24h |
High Priority | Impacting core functionality (offers, loyalty, ordering, sign-in) for many (<5%) users or hindering day to day operations for the business | 1h | Daily | 1 week |
Medium Priority | Impacting non-core functionality for many users or transient impact on core functionality | 24h | Weekly | 3 weeks |
Low Priority | Has a surmountable impact on the user experience for a significant majority of users | 24h | Weekly | 6 weeks |