Problem
Current bug reporting system is overcomplicated. This leads to frustration and keeps developers away from reporting (you can easily find tons of messages on the forum or on Twitter about it).
How can it be improved
1. Make it possible to report a bug right from the Bubble editor
Sometimes ago Bubble used to have bug reporting link in the editor (in Help section). But after transforming Help dropdown into a Help center sidemenu this link has disappeared.
Furthermore, don’t just redirect to the Report a bug page. Make it possible to fill all the details within the same app editor page.
Link to upvote on Bubble Ideaboard
2. Autofill fields that can be autofilled
This is a feature connected with the proposal above. As soon as you make it possible to report a bug from the editor - you can easily autofill info like Impacted application and Link to application editor.
Those who have a bunch of production and sandbox apps suffer from choosing an impacted application from the dropdown of the bug reporting page 
Link to upvote on Bubble Ideaboard
3. Change dropdowns to cards/tiles
Let’s see first steps to create a bug right now:
- Choose
When does this bug occur?
Dropdown with 4 options to chose from (app building, connecting a domain, connecting API and building a plugin).
Number of clicks: 2 (open dropdown and choose an option). - Choose
Is the bug in the application editor or run-mode?
Dropdown with just 2 options to chose from → application editor or run mode
Number of clicks: 2 (open dropdown and choose an option).
So we’ve just started our bug reporting process but we’ve already made 4 clicks just to choose 2 options from short lists. How to improve it? Replace such dropdowns to cards/tiles (so all options are shown simultaneously without any additional clicks) or toggle element (for two option lists). Like this:
Other dropdowns that can be replaced by cards/tiles:
Impacted version?How often does the bug occur?How is this bug impacting you?
So we can reduce 10 clicks (5 dropdowns values choosing) in a half just by using another UI element.
Link to upvote on Bubble Ideaboard
4. Make some Impact fields optional
When my app is completely down or app editor is crashing/loading for ages - there is no need to fill How often does the bug occur? and When did this last occur?information.
If you still need this info (I agree that it may be helpful in some cases) - make it mandatory for some How is this bug impacting you? options, but not for urgent incidents when app or editor are broken or have poor performance.
Link to upvote on Bubble Ideaboard
5. Implement bug/incident priority
Implement incidents priority (btw, I suppose Bubble has internal priority that is calculated based on impact info). As a follow-up/variant of previous idea. Replace How is this bug impacting you? with choosing a priority:
- Urgent → live app is broken, business processes can’t be carried out
- High → live app is not broken, but business processes are highly affected; app development is blocked
- Medium → some things are not working but can be worked around
- Low → other issues that have low impact on app live version and development process
Link to upvote on Bubble Ideaboard
6. Replace email support with a support center
After reporting a bug all further communication between bug reporter and Bubble support team is held via emails. There are 2 big disadvantages of such an approach from a reporter perspective:
- It’s not convenient. Especially when he needs to share additional images.
- It’s not easy to search for all bugs he reported in his email box.
I suppose Bubble for sure has a Service Desk system (some SaaS or custom solution). So grant reporters with an access to the system with all necessary authorisations. All we need is to have an access to all bugs we’ve reported and possibility to communicate with support team there.
