Bug Tracking doesn't answer my question. Developer will continue to assign it back, and QA would assign it forth... Back and forth... There should be some procedure outside the bug tracking system that regulates such conflicts. Corey, please approach answering the question with due seriousness.
In the absence of a well-defined process, why not start looking at the project team to see if there isn't someone who can sit in the middle and address this type of scenario...like a project manager.
As for where it might be outlined, a test plan might be a logical starting point. But, it depends on how you use your test plan document. For some, it's a living document...for others, it's nothing more than shelfware - created to meet a requirement, but never referred to after it is approved/signed off on/whatever the end-state is.
"The single biggest problem in communication is the illusion that it has taken place."
-George Bernard Shaw, Irish playwright and Nobel Prize winner, 1856-1950
PM (Project Management) will help you to address such disputes.PM should arrange a bug triage meeting along with the development(Lead) to resolve these kind of back and forth.hope this would help you to some extent.