Scope membership and version correctness answer different release questions.
The circularity problem
If fixVersion defines the population, an issue with a missing or incorrect version disappears before the version check can detect it. The gate then reports a smaller, misleading scope.
Separate scope from expectation
JQL_SCOPE defines the business population independently. The selected expected version then becomes a deterministic rule applied to every issue in that population. VERSION_ONLY remains available for simpler workflows.
Keep the missing issue visible
If DEMO-102 belongs to the release but has no fixVersion, the three-issue scope stays intact and DEMO-102 fails the version check. The release scope does not disappear because a Jira field is wrong.
Continue exploring
Read documentation