Fixed Status and Code Change
I have a doubt.
I had a doubt regarding a functionality. I have asked my technical and functional guys , on what basis the functionality is happening. They dont have any answer at that point on what basis its happening.
I logged my doubt in Quality Center as a bug, asking a question.
After some months, they all had a discussion regarding that bug and told me the condition. Am happy with the explanation.
Now they have rejected my bug, telling there is no code change in the bug and hence we are rejecting.
But i argued with them telling, because of that bug only, we got a clear cut answer regarding that functionality and so it should be fixed.
They rejected my plea and went forward and rejected it.
What should be the ideal scenario??
Re: Fixed Status and Code Change
A code change is not the only way of resolving a bug. We have a state called "No Action Required" instead than "Rejected". If any action is taken to resolve the bug, then the bug cannot be NAR. NAR is only valid if truly no action was taken. If a design change happened, an environment changed, server brought up that was accidentally down, etc. then the bug is set to "Released" and we can close it.
It has taken me a long time to get through to developers that a bug report does not have to have a code change to be resolved, but I have got there.