Get rejection reasons for rejected reproductions
complete
Markus Naumann
When a TL rejects a tester's reproduction, the tester only sees the status but no explanation. It is often incomprehensible for testers why the reproduction was rejected and they will not learn for the future. If the tester wants to know why, he or she needs to ask in the test chat, which causes more work for both the tester and the TL.
It would be very helpful if the TL provided a rejection reason. A prewritten rejection reason would help because then the tester would know what aspect of the reproduction was wrong.
Evgeniya Graich
complete
ted
As I understand it, this feature has been implemented.
The offer must be closed.
Анна Горбачевская
fully agree, it would be helpful
Veronica Aides
fully agree , is important to know "why"
H
Hossam
fully agree
Alexander Leonhard
What reasons would be relevant for reproductions?
Are those the same reasons as for bug rejects or are they different?
Sonja Radočaj
Alexander Leonhard: reasons for rejection would be: wrong attachment is added, date/time are not shown on the screencast, steps are missing in the reproduction, reproduction is too long, reproduction doesn't show the issue... maybe it should be possible to select more than one reason and add a comment.
Markus Naumann
Alexander Leonhard: They are different. TLs should ideally just select an appropriate reason via a dropdown menu without having to manually enter a rejection reason as it is the case for bug reports.
Here are my suggestions in order of relevance:
- "Incomplete evidence of the bug"
- "Screencast too long" (or split into two: "Screencast longer than 10 seconds" & "Screencast longer than original screencast")
- "Screencast was required" (screenshot was uploaded instead, which does not prove the bug)
- "Screenshot was required" (screencast was uploaded instead, which as unnecessary and leads to more work for the TL)
- "Current date not displayed"
- "URL bar not displayed"
- "Reproduced invalid report" (e.g. submitted as functional although it is a content bug, and content reports do not support reproductions).
- "Wrong reproduction status"
- "Mismatch with selected environment"
- "Crash log missing"
Multiple reasons might apply as pointed out by Sonja, so instead of a dropdown menu, checkboxes could also be a solution.
ted
Markus Naumann: Hi.
Thus, these reasons will help in the future to make reproductions cleaner and increase the approval rating of the reproductions themselves.
M
Meadde
Yes it would help us to improve the quality of our work.
manpreet k
Yes, this would be very helpful
Asa
Yes just like bug rejection reasons so as there should be a reproduction rejection reason