[PM-38210] Remove access-intelligence-trend-chart feature flag#21376
[PM-38210] Remove access-intelligence-trend-chart feature flag#21376lastbestdev wants to merge 1 commit into
Conversation
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE This PR unwinds the Code Review DetailsNo findings. The flag removal is complete and consistent across both component versions, the updated tests properly exercise the new on-init and org-id-change initialization paths, and the intentionally retained |
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #21376 +/- ##
=======================================
Coverage 49.20% 49.20%
=======================================
Files 4074 4074
Lines 127810 127788 -22
Branches 19565 19563 -2
=======================================
- Hits 62889 62879 -10
+ Misses 60266 60254 -12
Partials 4655 4655 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|



🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-38210
📔 Objective
Unwind the
pm-26961-access-intelligence-trend-chartfeature flag, which has completed rollout. The trend chart on the Access Intelligence activity dashboard is now permanently enabled.Changes:
AccessIntelligenceTrendChartfromFeatureFlagenum andDefaultFeatureFlagValue(libs/common/src/enums/feature-flag.enum.ts).activity-tab.component(v2) andall-activity.component: removed the flag gate so the trend widget always renders; theRiskOverTimeServiceis now initialized unconditionally when the organization id is available.extendPasswordChangeWidget/setExtendPasswordWidgetand theNgClassusage) that only existed in the flag-off layout branch.flagEnabledoption +ConfigServiceprovider) and renamed theTrendChartEnabledstory toTrendChart.activity-tab.component.spec.tsto drop the flag-based tests and assert the trend chart initializes on init and re-initializes when the organization id changes.The shared
AllActivitiesService.extendPasswordChangeWidget$observable and the childPasswordChangeMetricV2Component.extendWidgetoutput were left in place as they are existing public APIs outside the scope of this flag.📸 Screenshots
N/A — no net visual change for users who already had the flag enabled.
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:) or similar for great changes:memo:) or ℹ️ (:information_source:) for notes or general info:question:) for questions:wrench:) 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