# 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 <a href="#bug-report-instructions" id="bug-report-instructions"></a>

![](https://394991609-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MSUfI_fG0ZsLhSyhmV_%2F-MSUmOL7obW2Y6VmGExl%2F-MSUmXkRDrOJtorOYcpX%2Fimage.png?alt=media\&token=5a1dc2ad-056e-4087-ab12-4d9c62f86e68)

#### **Step-by-step guide:** <a href="#step-by-step-guide" id="step-by-step-guide"></a>

1. Open the form BUG REPORT FORM
2. Input all information regarding the bug
3. Submit the form
4. 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 <a href="#feature-request-instructions" id="feature-request-instructions"></a>

![](https://394991609-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MSUfI_fG0ZsLhSyhmV_%2F-MSUmOL7obW2Y6VmGExl%2F-MSUmjvLePzush3nU7Pv%2Fimage.png?alt=media\&token=c9e79345-b1ff-4c25-9868-d4a75e82f058)

#### Step-by-step guide: <a href="#step-by-step-guide-.1" id="step-by-step-guide-.1"></a>

1. Open the form FEATURE REQUEST FORM
2. Input all information regarding the Feature you want to be added / developed
3. Submit the form
4. 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: <a href="#review-process-for-both-bugs-and-features" id="review-process-for-both-bugs-and-features"></a>

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
