During my seven years as transition and support lead in Shell, I often been asked how to deal with issues at release point. The project manager generally wants to push the release because the budget is tight and the pressure of the deadline is becoming tangible. The user community, IT operations and information security stakeholders are reluctant to mandate the release, because they are concerned the issues will disrupt operations or will remain unresolved and cause pain for years to follow.
Our guidance has always been quite simple and effective. Do a risk assessment on the issue and then prioritize. Same practice is applied in OPSASTO. Categorisation takes place using a RISK ASSESSMENT MATRIX that in turn drives the prioritisation following a PRIORITISATION MATRIX. Once you agree on this approach, the debate can be about the impact and you can prevent wasting energy debating different perspectives of the truth.