Bugs workflow

New boards

Deprecated boards

​We have deprecated multiple boards and channeled them into one.

1. ​Bugs(Admin and Join)

2. Paid Org Bugs

3. Backend bugs

4. User stability

1. ​Bugs

2. Feature requests

1. ​All incoming bugs get added to the #inbox section.

​2. Prioritization: Weekly calls with the team leads to prioritize the bugs.

​3. Once engineers have deployed the fix, the Customer Success team verifies and moves them to the closed section.

​Bugs priority:

1. P0 (Drop everything & fix)

2. P1 (Fix in a week)

3. P2 (Fix in a month)

​

Bug status for the teams:

1. Not Started

2. On Track

3. Delayed

4. Merged

5. Fixed

6. Closed

7. Won't Fix

​ Why do this? (Expected outcomes)

1. Stable product with high user satisfaction.

2. Ensure the fixes are shipped on time according to the priority. ​

​​

Things to note:

1. Test the product thoroughly before deploying the fix.

2. A bug fix should not create a new bug.

3. If you are unable to recreate, reach out to the CS team to get more information.