I am just a little bit disappointed at this point with support at Bubble generally. It seems like with the non-stop issues that are happening in the editor and the public response from @josh and @Roody_BubbleSupport asking the community to continue to submit bug reports, that there would be a bit more effort on Bubble side to ensure that support is top-notch and all user interactions with support are positive.
I have many positive experiences with support, but as the saying goes, one bad appleâŚI donât know I forget the rest of the expression as I just focused on the one bad apple part.
One experience in particular is really irking me right now and I need to vent publicly in the hopes it might lead to positive change within how support works. My past public rants and frustration vents led to some significant changes that helped improve the support process. I spoke with support agents in attempts to find what would be more helpful for them when reporting bugs, and that is where the video submission piece came in from. Iâve had support agents tell me, they love working on my bug reports because I provide videos and everything else they might need to make their investigation quicker and result in a resolution more easily.
As I am sure, others are like me, in that a lot of times we might report bugs that are not actually bugs, but maybe we as the developer are doing something wrong, or there is a known limitation or that maybe the system just works differently than we may have expected.
I believe this case below highlights something a little bit different from that.
On august 10 I submitted via email a bug (sometimes it takes too much of my time to go through the report - especially when it is related to âeditor issuesâ). The bug report had the following video attached to it, which demonstrated that when there is a conditional and the property to change is the datasource, the clear expression function does not clear the expression, instead it deletes the property to change.
The response was the following:
I appreciate you taking the time to explain your frustration with this - the clear expression behavior as you describe it is working as expected, however I will be sure to pass your feedback on to our product team for their consideration.
Additionally, this would be an excellent point to share on our Ideaboard, which allows you to submit feature requests and vote on ideas that other users have shared. Our product team regularly monitors this and uses it to inform our roadmap.
Then on August 11 I followed up with another video that explained and demonstrated that when I have a conditional and the property to change is text, and I use the clear expression function, the clear expression function will clear the dynamic expression and the property to change (text) remains open.
I followed up with this video and demonstration because I felt that if the behavior of clear expression is working as expected for the property to change of text, then it should work the same way when the property to change is datasource.
The response on August 24 was the following:
Thanks for your patience with this - the engineering team just clarified that the âclear expressionâ function deleting a data source parameter and emptying a text parameter is working as expected.
Iâve passed along the feedback that this is inconsistent and confusing to our users.
It just seems like there is a tendency to reply that legitimate Bugs are âworking as expectedââŚand even if they are working as expected, the working as expected from the engineering teams perspective seems to completely disregard the expectations of the users of the system, and are just simply providing for an extremely poor user experience.
I really hope this open rant will again help to improve the support process at Bubble to make it so that my and many other users continued efforts at improving Bubble as a platform through our unpaid efforts at reporting bugs is not in vain, and instead result in tangible improvements to the platform.
