Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
With a lot of the issues I have raised that the team has resolved previously, I’ve noticed that they reappear after Bravo Vision undergoes a new update. Having already taken a lot of effort to open a ticket, communicate with customer support, and wait for the dev team to look into the issue and fix it, now I have to repeat the process all over again, once, twice, three times. The reappearance of resolved issues not only is a waste of our resources, but also impacts our app users continuously after we tell them the issue has been resolved.
This actually poses a great risk of losing users on our platform.
Considering 1) how inefficient it is to fix the same issues over and over again, 2) how much each issue impacts and re-impacts our users, and 3) this sentiment is echoed by other Bravo users as well, I urge the Bravo dev team to explore ways to track resolved issues in a more organized manner and conduct QA in the testing environment more comprehensively in relation to the already resolved issues.
19 replies
Wrote something in this thread and want it removed? Request removal
Ask the community on Discord
This archive is read-only. New questions, office hours and product updates now happen in the Bravo Discord.
Join the Discord