-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PM-11503] Organization Automatic Sync verbiage is misleading #11151
[PM-11503] Organization Automatic Sync verbiage is misleading #11151
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #11151 +/- ##
==========================================
- Coverage 35.08% 33.17% -1.92%
==========================================
Files 2709 2727 +18
Lines 84530 85192 +662
Branches 16067 16208 +141
==========================================
- Hits 29661 28265 -1396
- Misses 53898 54675 +777
- Partials 971 2252 +1281 ☔ View full report in Codecov by Sentry. |
New Issues
Fixed Issues
|
"billingTokenSyncDesc": { | ||
"message": "Billing sync unlocks Families sponsorships and automatic license syncing on your server. After making updates in the Bitwarden cloud server, select Sync License to apply changes." | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
billingSyncDesc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This message key is defined, but not used anywhere.
❓ Is it possible that billingSyncDesc
was supposed to be replaced with billingTokenSyncDesc
, but you then introduced automaticBillingSyncDesc
as the final replacement? If my assumption is correct, then please remove billingTokenSyncDesc
from en/messages.json
apps/web/src/app/billing/organizations/organization-subscription-selfhost.component.html
Show resolved
Hide resolved
apps/web/src/app/billing/organizations/organization-subscription-selfhost.component.html
Show resolved
Hide resolved
apps/web/src/app/billing/organizations/organization-subscription-selfhost.component.html
Show resolved
Hide resolved
"billingTokenSyncDesc": { | ||
"message": "Billing sync unlocks Families sponsorships and automatic license syncing on your server. After making updates in the Bitwarden cloud server, select Sync License to apply changes." | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"billingTokenSyncDesc": { | ||
"message": "Billing sync unlocks Families sponsorships and automatic license syncing on your server. After making updates in the Bitwarden cloud server, select Sync License to apply changes." | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This message key is defined, but not used anywhere.
❓ Is it possible that billingSyncDesc
was supposed to be replaced with billingTokenSyncDesc
, but you then introduced automaticBillingSyncDesc
as the final replacement? If my assumption is correct, then please remove billingTokenSyncDesc
from en/messages.json
446c610
…omatic-Sync-verbiage-is-misleading-2' into PM-11503-Defect-Organization-Automatic-Sync-verbiage-is-misleading-2
213f9d3
🎟️ Tracking
📔 Objective
📸 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