[PM-41100] fix: Complete the VFO-1 organization-to-vault revert - #7220
Conversation
The revert of the VFO-1 naming changes (#7195) missed the "organization" to "vault" rename entirely: it correctly reverted the Owner and Collections wording but left "Move to vault", the Move-to-organization dropdown label, and their supporting/empty-state text unconditionally showing the new terminology, and never restored the move_to_organization/move_to_org_desc/no_orgs_to_list strings. Restores those strings, points the affected screens/ViewModel back at them, and removes the leftover move_to_vault/no_vaults_to_list strings, so the app fully matches its pre-VFO1 baseline again until the flag-gated version (stacked behind vfo1-foundation) lands.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7220 +/- ##
==========================================
- Coverage 86.36% 86.21% -0.15%
==========================================
Files 916 888 -28
Lines 65833 64820 -1013
Branches 9718 9706 -12
==========================================
- Hits 56854 55883 -971
+ Misses 5509 5468 -41
+ Partials 3470 3469 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE Reviewed the completion of the VFO-1 organization-to-vault revert across five production files, three Compose test files, and Code Review DetailsNo findings. The revert is faithful to the pre-VFO1 baseline and self-consistent between production code, string resources, and tests. |
There was a problem hiding this comment.
Pull request overview
This PR completes the revert of the VFO-1 “Organization → Vault” terminology changes by restoring the original “Organization” wording and associated string resources in the “Move to Organization” flow, aligning main back to the pre-VFO1 baseline until the feature-flagged work lands.
Changes:
- Restores
move_to_organization,move_to_org_desc, andno_orgs_to_listusage in the Move-to-Organization UI/ViewModel and removes the defaultmove_to_vault*strings fromvalues/strings.xml. - Updates Compose UI and ViewModel logic to reference the restored organization strings.
- Updates Compose UI tests to assert “Move to Organization” and related accessibility/text content.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| ui/src/main/res/values/strings.xml | Restores organization-based strings in the default locale resources. |
| app/src/main/kotlin/com/x8bit/bitwarden/ui/vault/feature/movetoorganization/VaultMoveToOrganizationViewModel.kt | Switches app bar title text back to move_to_organization. |
| app/src/main/kotlin/com/x8bit/bitwarden/ui/vault/feature/movetoorganization/VaultMoveToOrganizationEmpty.kt | Switches empty-state string back to no_orgs_to_list. |
| app/src/main/kotlin/com/x8bit/bitwarden/ui/vault/feature/movetoorganization/VaultMoveToOrganizationContent.kt | Switches dropdown label/supporting text back to organization terminology. |
| app/src/main/kotlin/com/x8bit/bitwarden/ui/vault/feature/item/VaultItemScreen.kt | Updates overflow action label back to move_to_organization. |
| app/src/main/kotlin/com/x8bit/bitwarden/ui/vault/feature/addedit/VaultAddEditScreen.kt | Updates overflow action label back to move_to_organization. |
| app/src/test/kotlin/com/x8bit/bitwarden/ui/vault/feature/movetoorganization/VaultMoveToOrganizationScreenTest.kt | Updates UI test assertions to match “Organization” wording. |
| app/src/test/kotlin/com/x8bit/bitwarden/ui/vault/feature/item/VaultItemScreenTest.kt | Updates UI test assertions to match “Move to Organization”. |
| app/src/test/kotlin/com/x8bit/bitwarden/ui/vault/feature/addedit/VaultAddEditScreenTest.kt | Updates UI test assertions to match “Move to Organization”. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| <string name="move_to_organization">Move to Organization</string> | ||
| <string name="no_orgs_to_list">No organizations to list.</string> | ||
| <string name="move_to_org_desc">Choose an organization that you wish to move this item to. Moving to an organization transfers ownership of the item to that organization. You will no longer be the direct owner of this item once it has been moved.</string> |
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-41100
📔 Objective
The revert of the VFO-1 naming changes (#7195) squashed three separate PRs (#7183 Owner, #7189 Collections, #7192 Organization→Vault) into one commit. It correctly reverted the Owner and Collections wording everywhere, but missed every hunk belonging to the Organization→Vault rename — including two files (
VaultMoveToOrganizationContent.kt,VaultMoveToOrganizationEmpty.kt) that PR #7192 was the only one of the three to touch, so they never surfaced while resolving the other two.As a result,
mainwas still unconditionally showing "Move to vault" (menu item, app-bar title, dropdown label, description, empty-state) regardless of any feature flag — exactly what QA caught in this ticket.This PR completes the revert: restores
move_to_organization,move_to_org_desc, andno_orgs_to_list, points the affected screens/ViewModel back at them, and removes the leftovermove_to_vault/move_to_vault_desc/no_vaults_to_liststrings — so the app matches its pre-VFO1 baseline again until the flag-gated version (already stacked behindvfo1-foundationin #7219) lands.📸 Screenshots