Follow up bugs or tasks procedure

This document contains how to follow up on bugs or tasks. In Hungry Hub, we use Basecamp as our project management tool which is not only a task-based ticket but also includes deflect / bug.

Follow up on bugs and task differences.

• Follow-up bug: Re-checking the bug ticket that has been added according to the standard bug ticket during development or escalation bug ticket and has been checked or fixed by Dev or another role.
• Follow-up task Project: Test the feature or task that has been implemented by the programmer according to the scope.

Request to QA procedure.

Once the ticket has already been fixed or implemented, here is the procedure to request QA to check the ticket.

1. Add QA name to the assigned to
2. Add a comment to the ticket and mention the QA with detailed information which can help QA to check the request.
3. Inform the PR link in the comment.

How to confirm/close the ticket?

After QA gets a request, QA should follow up on the ticket accordingly.

1. Check the ticket on the correct environment, and build/link according to the request.
2. DO NOT confirm the ticket before the bug is fixed correctly or the task is implemented correctly, mention the related PRG and add a new proving image/video for the issue.
3. If there is another bug that occurs after the implementation, please create another ticket about it.
4. When the bug has already been fixed, please close the ticket and add relevant information to the ticket (in which build/link the bug already fixed, or provide the proving image/video if necessary)