Redeploying a tenanted release and including tenants that already have that release creates a deployment even if selecting to skip tenants with that release

[hnrkndrssn]

Severity

UI confusion, unnecessary deployments created

Version

All versions, code hasn't changed since introduced

Latest Version

I could reproduce the problem in the latest build

What happened?

When redeploying to a single Tenant, the Skip tenants where <version> is the current version deployed to <environment> doesn't seem to work as expected.

What I expected: If ticked, and the Tenant is already running the current version, there should be no deployment created.

What happens: When ticked, and the Tenant is already running the current version, a deployment is created anyway. This is confusing because I'm not sure why the box is ticked if it doesn't take effect

Reproduction

Create a project
Create an environment
Attach a tenant to the project and environment
Create a release
Deploy the release to the environment
Select to redeploy the release to the same environment
Select the tenant
Observe deploy button is enabled and preview shows that a deployment will be created for the tenant

Error and Stacktrace

No response

More Information

No response

Workaround

No response

[octoreleasebot]

Release Note: Fix redeploy tenanted release issue where the option to skip tenants where release is current for a tenant isn't available after explicitly selecting tenants

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2023.1	2023.1.11970
2023.2	2023.2.13175
2023.3	2023.3.11120
2023.4+	all releases