Follow up bugs or tasks procedure
This document describes how to follow up on bugs or tasks. In Hungry Hub, we use Basecamp as our project management tool used for managing both task-based tickets and bug tickets.
Follow up on bugs and task differences.
- Follow-up bug: A follow-up bug involves re-checking a bug ticket that was added according to standard procedures during development or escalation and has been checked or fixed by Dev or another role.
- Follow-up task Project: A follow-up task project involves testing 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.
- Assign the ticket to the QA by adding their name in the “Assigned to” field.
- Add a comment to the ticket and mention the QA with detailed information that will help the QA team verify the request.
- 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.
- Check the ticket in the correct environment, and build/link according to the request.
- Do not confirm the ticket until the bug is fixed or task is implemented correctly.
- Mention the related PR and add new proving media.
- If there is another bug that occurs after the implementation, please create another ticket about it.
- When the bug has already been fixed, please close the ticket and add relevant information to the ticket (in which build/link the bug has been fixed, or provide the proving image/video if necessary).