TeamCity “N changes” badge compares to default branch, not PR target

Context

• We run PR builds in TeamCity on Windows agents.
• Many PRs target release/ branches (not the default branch).
• In the UI, the small “N changes” pill shows far more changes than the PR actually introduces.

Actual behavior

• The “N changes” badge is always calculated against the VCS root’s default branch.
• For PRs targeting a release branch, this inflates the count (it’s effectively delta vs main).

Expected / desired behavior

• Have that badge (or an option) compute changes relative to the PR target branch.
• Alternatively, expose a built-in variable/setting to switch the comparison basis in the UI.

Why it matters

• For multi-branch release flows, the default-branch delta misrepresents scope and causes noise.
• We are conditionally triggering build steps based on type of changed files. This behavior introduces false positives.

Steps to reproduce

1. Configure a VCS root with default branch = main.
2. Create a PR from feature/x → target release/4.5.
3. Observe the “N changes” badge shows the diff vs main, not vs release/4.5.

Would be grateful if someone could help me figure out this issue. One way to solve it would be separating out the Build Configuration and specifying a different default branch for each one. But this would complicate our setup and GitHub build checks and introduce overhead for our branching workflow.