100%
Even more to that is the now automatic closing of tickets. I sent a bug report on March 27 asking Bubble support to look at their logs to see why an option value was not getting stored correctly (workflow action is set to a single option of confirmed, but my app logs show it saved as started, which causes a chain reaction in a live app with real users and real money involved).
After waiting until March 30th to hear a response, which was that support can see the issue and after checking their logs can confirm the issue exists, but in order for them to send to engineering I need to provide steps to reproduce.
Thanks a lot for waiting! I was able to look at the logs and I do see that the ‘status_option_task’ was set to ‘started’ as opposed to what should have been ‘confirmed’. In order for us to investigate, we do need to be able to reproduce and dig a bit deeper to investigate and provide you with a resolution or file a report to the engineering team who will need to reproduce this behavior again to investigate on their end.
Why in the world would they need steps to reproduce? They have access to the logs that show every single step involved, and in even greater details than we can access in our own app logs. All engineering would do is follow the steps and then look at the logs to see what happened. Why is it impossible for them to just look at the logs for the specific instance of the bug causing a problem to figure it out?
Then 3 days later on April 2nd I get an email that the ticket has been marked as resolved and closed.
You recently contacted our team for assistance, and we wanted to note that your Support inquiry has been marked as resolved and its associated ticket has been closed.
In my mind, that is a real pathetic way to get the numbers up for showcasing in the monthly community update how many Bug tickets get closed and resolved in how many days. A vanity metric that shows no real insights into the every increasingly maddening support that is provided by Bubble (not the support agents, they are just working as cogs in the machine - it is the machine architect to blame).
So, now what? Because I don’t have enough free time to jump when Bubble support instructs me to jump I have to go through the whole process again? I have still yet to reply to see if the ticket is going to get opened again or if I will be met with a likely response of ‘this ticket is closed, please submit a new bug report’.
UPDATE
This is as expected and it is maddening
Not only maddening that they closed the ticket and I need to create a new one, but also maddening because the Bug has degraded the data integrity even further