Tester Feedback

Hello, Currently, testers face a limitation: they can't leave feedback once a test cycle ends. This poses a problem because testers often prioritize bug hunting over providing feedback, leaving them with insufficient time to share their insights before the cycle concludes. Why Implement This Change? Testers' Focus: During busy test cycles, testers are primarily focused on identifying and reporting bugs, which can lead to neglecting feedback submission. Insightful Input: Allowing feedback submission after the cycle ends enables testers to provide more thoughtful and insightful input as they become increasingly familiar with the app/website through testing. Proposed Solution: Extended Feedback Time: Users should retain the ability to submit feedback even after a cycle ends, possibly until the test is archived. Eliminating Rush: This approach eliminates the rush to provide feedback, allowing testers to allocate more time for thoughtful responses as their primary focus shifts from bug hunting to feedback provision. Implementation Benefits: Relevant Feedback: This improvement leads to the submission of more relevant and valuable feedback for the customer, enhancing the overall quality of the product/cycle. Tester Empowerment: Empowering testers to contribute effectively to the improvement of the app/website without compromising bug reporting priorities enhances the efficiency and effectiveness of the testing workflow. Thank you.

Icons of testers without added profile pictures, and icons of team leaders are the same. For example, when you read a chat, it would be convenient to find the messages of the team leader in the chat, by the original avatar icon, which belongs only to the team leaders.

In repetitive test cycles, I as a tester would like to know which are the comparatively newly added features by looking at the known bugs count. This will help me target newer sections of the app or features which haven't been thoroughly tested yet

Some tests have mobile apps and, in the app, the download link have a space, so it's not clickable. If every link was clickable, that would help us a lot.

The same ways things were last year are not how things will be this year. We should be getting significant increase in payout per bug across board this year so as to motivate us more as a tester.

The new filter menu is convenient and has more filtering options, but there is no indicator for the number of reported bugs for features and types. Some test cycles have a limit on the number of bugs, for example only 10 Low bugs. Therefore, to determine the number of bugs already reported, testers need to apply a filter and see how many bugs have already been reported. This is inconvenient, especially since sometimes testers delete their reports and thus the number changes. In the previous filter menu, the drop-down menu showed the number of reported bugs with features or bug types. I suggest adding a bug counter to the filter menu.

I add reproduction for an issue, I delete it and when I add a reproduction again it does nothing (the page just refresh and nothing happen)

In today's world, many no longer use email all the time. All modern people, especially young people, have long used messengers to communicate. I would like new test notifications to come to my phone number in Viber, WhatsApp, Telegram or at least as sms. This is much more convenient than an email and hard to miss.

Hello, From my perspective, The idea of requesting a payment and waiting 10+ more days for it to be processed is a little bit discouraging. I hope this is comfortable for the platform

Each team leader has his own criteria for making bugs. The same bugs different TL reject for opposite reasons. Already, many times the bugs that some TL forwaded and the customer accepted were rejected by other TL. One TL considers the error visual, the other considers the error as functional. TestIO academy rarely help reach agreement.