Improved QA Flow for Bug Testing

Problem The current bug-testing process is inefficient, especially when multiple bugs are fixed at the same time. Testers are often notified through many separate Telegram messages saying that specific bugs are ready for testing. This creates unnecessary spam and makes the process hard to follow. Users then have to switch back and forth between Telegram and the website, search for old messages, remember what each ticket was about, and manually find the related context before testing. This slows down validation and makes QA much less convenient. Proposed Solution Create a dedicated Bugs Leaderboard / Bugs QA Page on the website that serves as the main place for bug validation. When a bug is fixed, it should automatically appear on this page with the status Ready to Test. Testers should be able to open the bug detail directly on the website, see what the issue was, understand what was changed, and test it immediately without needing to search through Telegram history. QA Workflow Each bug should support a simple review flow: Ready to Test – developer marks the fix as ready for validation Approved – bug creator or tester confirms the fix works In Progress – if the issue is not fully fixed, the tester can add a comment and move it back for more work The bug creator should be able to: open the bug detail review the fix add comments if something is still wrong approve the fix if it works change the status back to In Progress if more work is needed Result This would make QA much more organized, reduce Telegram spam, and give users one clear place to test and validate bug fixes. It would also make the whole feedback loop faster, clearer, and much easier to manage when many bugs are being fixed in parallel.