Renaming a tag in a Target-scoped TagSet silently breaks deployment target roles

[HuyPhanNguyen]

Severity

No response

Version

2026.2

Latest Version

I could reproduce the problem in the latest build

What happened?

Renaming a tag in a Target-scoped TagSet succeeds with no warning, but doesn't update the places that store the tag by name. Deployment target Roles, process step role scoping, runbook triggers, etc.

Expected: either cascade the rename to all references in one transaction.

Reproduction

1. Create a TagSet scoped to Targets (e.g. "Environment-Type") with a tag "web".
2. Apply the "web" tag to one or more deployment targets.
3. Create a deployment process step scoped to the "web" role.
4. Create and deploy a release (this freezes the process snapshot with role "web").
5. Optionally enable Config-as-Code on the project and commit; the OCL on disk references "web".
6. Rename the tag from "web" to "web-server" in the TagSet editor. No warning is shown. Save succeeds.
7. Observe:
   • The deployment target still shows role "web" in its target tags collection.
   • Editing and the deployment target will show missing icon on "web" tag

Error and Stacktrace

More Information

No response

Workaround

No response