May 7
Cycle Feedback Feature Enhancement: Extending Submission Period Beyond Cycle End
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.
Completed