There is nothing more frustrating then spending an inordinate amount of time researching a potential bug, scouring the repository to see if it already exists, running through various scenarios to try and reproduce, talking to SMEs, documenting the issue, setting up meetings and phone calls to discuss, etc, only to find out… the issue does not matter!
Some examples may be:
a) Being rejected by the stakeholder as not important, and thus will not get fixed
b) Falling into the cesspool, that is the bug repository, where it will sit, sight unseen for eons
c) Lowering the severity to where it ‘may’ be fixed at some point
d) Being cast as ‘something that a user would never do’ and dismissed
Often, what we think may be a show-stopper or a higher priority issue, is not viewed that way by others. As testers, we have a unique outlook on things, and can bring a different perspective. Certainly from a UX level, we can provide valuable input.
Here are a few suggestions that may help:
1. Sell yourself and the issue – I have found many instances of issues that I’ve raised, that were decided to never be fixed, only to have customers raise them as high-priority issues at a later date. Don’t be afraid to stand up, be counted, and explain why this issue matters.
2. Consult a second opinion – what may not be a big deal to one, may be a big deal to another. There are always multiple irons in the fire. Create a discussion. It is better to be fixed and found now and certainly much less costlier then doing it later.
3. Review the issue at a later date – what may have been dismissed earlier, may be taken more seriously as the product is/has evolved.
4. Accept it as what it is – sometimes we need to do this. We can’t fix every bug, and it may very well be that it is not important to be fixed, or will be back-burnered until the end of time.
Don’t be offended, sell yourself, sell the issue, consult second opinion(s), review later, accept.
It can be hard to do all these things, but in the end, each has its place.