[PR #6273] [MERGED] [PM-29842] Add organization event types for item migration acceptance and rejection #48049

Closed
opened 2026-04-26 15:34:44 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/6273
Author: @SaintPatrck
Created: 12/15/2025
Status: Merged
Merged: 12/16/2025
Merged by: @david-livefront

Base: mainHead: PM-28472/org-event-types


📝 Commits (1)

  • 15ac0cf [PM-28472] Add organization event types for item migration acceptance and rejection

📊 Changes

2 files changed (+26 additions, -0 deletions)

View changed files

📝 app/src/main/kotlin/com/x8bit/bitwarden/data/platform/manager/model/OrganizationEvent.kt (+20 -0)
📝 network/src/main/kotlin/com/bitwarden/network/model/OrganizationEventType.kt (+6 -0)

📄 Description

🎟️ Tracking

PM-29842
Relates to https://github.com/bitwarden/server/pull/6721

📔 Objective

Introduce new organization event types to track user decisions regarding the migration of personal ciphers to an organization's "My Items" folder, typically triggered by personal vault ownership policies.

Actual event tracking will be implemented in a subsequent PR.

Specific changes:

  • Update OrganizationEventType in the network layer to include ORGANIZATION_ITEM_ORGANIZATION_ACCEPTED (1618) and ORGANIZATION_ITEM_ORGANIZATION_DECLINED (1619).
  • Add corresponding data objects ItemOrganizationAccepted and ItemOrganizationDeclined to the OrganizationEvent sealed class hierarchy to handle these events within the application logic.

Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/6273 **Author:** [@SaintPatrck](https://github.com/SaintPatrck) **Created:** 12/15/2025 **Status:** ✅ Merged **Merged:** 12/16/2025 **Merged by:** [@david-livefront](https://github.com/david-livefront) **Base:** `main` ← **Head:** `PM-28472/org-event-types` --- ### 📝 Commits (1) - [`15ac0cf`](https://github.com/bitwarden/android/commit/15ac0cf6ebde84b3359588d429e2a293f984886a) [PM-28472] Add organization event types for item migration acceptance and rejection ### 📊 Changes **2 files changed** (+26 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `app/src/main/kotlin/com/x8bit/bitwarden/data/platform/manager/model/OrganizationEvent.kt` (+20 -0) 📝 `network/src/main/kotlin/com/bitwarden/network/model/OrganizationEventType.kt` (+6 -0) </details> ### 📄 Description ## 🎟️ Tracking PM-29842 Relates to https://github.com/bitwarden/server/pull/6721 ## 📔 Objective Introduce new organization event types to track user decisions regarding the migration of personal ciphers to an organization's "My Items" folder, typically triggered by personal vault ownership policies. Actual event tracking will be implemented in a subsequent PR. Specific changes: - Update `OrganizationEventType` in the network layer to include `ORGANIZATION_ITEM_ORGANIZATION_ACCEPTED` (1618) and `ORGANIZATION_ITEM_ORGANIZATION_DECLINED` (1619). - Add corresponding data objects `ItemOrganizationAccepted` and `ItemOrganizationDeclined` to the `OrganizationEvent` sealed class hierarchy to handle these events within the application logic. ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-26 15:34:44 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#48049