codecov[bot]
commented
2 days ago Codecov Report
Attention: Patch coverage is 27.77778% with 52 lines in your changes missing coverage. Please review.
Project coverage is 33.41%. Comparing base (
e6c68b7) to head (756c2a7).
:white_check_mark: All tests successful. No failed tests found.
Additional details and impacted files
```diff @@ Coverage Diff @@ ## main #12056 +/- ## ========================================== - Coverage 33.42% 33.41% -0.01% ========================================== Files 2871 2872 +1 Lines 89791 89857 +66 Branches 17098 17113 +15 ========================================== + Hits 30012 30029 +17 - Misses 57417 57459 +42 - Partials 2362 2369 +7 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
🚨 Try these New Features:
- JS Bundle Analysis - Avoid shipping oversized bundles
github-actions[bot]
Checkmarx One – Scan Summary & Details – 
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-13347
📔 Objective
When the Remove Bitwarden Families policy is on, the product will follow the following behaviors depending on the # of organizations the user is part of.
Individual vault impacts - Scenario 1
Given the users email address is only associated with 1 enterprise organization, when the policy is turned on, then hide the Free Bitwarden Families page from the navigation
Individual vault impacts - Scenario 2
Given the email address is associated with multiple enterprise organization, the policy is turned on, and my sponsorship is status is active, when the user attempts to interact with the three dot menu, then the only option is to remove the sponsorship
Individual vault impacts - Scenario 3
Given the email address is associated with multiple enterprise organization, the policy is turned on, and my sponsorship is status is sent, when the user attempts to interact with the three dot menu, then the only option is to remove the sponsorship and we hide the Resend email option
📸 Screenshots
⏰ Reminders before review
🦮 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