Bug Badminton: The frustrating "game" of reassigning a bug report back and forth between engineering and QA.
The number one thing you must have in your bug reports in order to avoid bug badminton is:
Result & Expected Result
The Result is what actually happened.
The Expected Result is what you thought was going to happen.
You can't assume that what you thought was going to happened is what the engineer thought would happen. The result may be what they actually intended. Perhaps they didn't look at the product the same way you are using it and your idea is better.
Perhaps it actually is as required, specified and designed and the bug report should be closed or you can assign it to the Project Manager and make a case for why your Expected Result is indeed what the user will expect.