Hi community,
As part of adding dashboard graphs and monitoring to one of my organization teams,
I want to learn and analyze why bugs are rejected by the dev team in terms of segmentation and cause.
I want to be able to define our rejected bugs are caused mainly by 3 reasons:
1. Reason W.
2. Reason Y.
3. Reason Z.
My expectation is to see in a visual way (graph or some chart) the total number of bugs that were rejected by the team according to the segmentation of the reasons for which they were rejected.
In addition. it will be nice to see the "top X leading reasons" in some way.
Of course, I'd rather get free solutions over paid ones.
Appreciate your help.
Thanks,
Dean
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.