Submit a Bug Report or Feature Request
This guide covers the process of reporting a bug and/or submitting a feature request to the product and tech teams.
What is the difference?
A bug is a discrepancy between how code is actually working and how our code was intended to work. A feature request requires new code to satisfy a case that can't be handled by the current codebase.
Bug report Instructions
Step-by-step guide:
Open the form BUG REPORT FORM
Input all information regarding the bug
Submit the form
Review your submission in the Bug Inbox project BUG BOARD
Do not skip details in the form and try to be as precise as possible please. A bug investigation is like a criminal case, every detail matters to find the cause of the issue!
CRITICAL issues affecting business or users severely should be immediately reported via the #tech-emergency channel on Slack (website or payment down, cancelling classes do not work, etc.).
Feature request Instructions
Step-by-step guide:
Open the form FEATURE REQUEST FORM
Input all information regarding the Feature you want to be added / developed
Submit the form
Review your submission in the Bug Inbox project FEATURE REQUEST BOARD
For feature requests, the most important for us (Product) is to understand the problem that you are trying to solve for customers, coaches or yourself.
After submitting your request, we will review it and follow up accordingly for clarification and definition of the problem / solution assessment.
Review process for both bugs and features:
The team is reviewing all new submissions on a weekly basis and moving tickets according to the flows above.
If a bug report is critical → please advise us immediately
If your bug report is rejected, you will be informed why
If your feature request is rejected after review and clarification, you will be informed why
You can follow the status of a submission directly from the Asana projects boards
If you have any questions, please approach Product team directly on Slack or at the office
Last updated
Was this helpful?