Skip to content

feat(ui): Productivity pilot reusing the analytics dashboard (U5 B2)#440

Merged
OBenner merged 1 commit into
developfrom
claude/ui-b2-productivity
Jul 24, 2026
Merged

feat(ui): Productivity pilot reusing the analytics dashboard (U5 B2)#440
OBenner merged 1 commit into
developfrom
claude/ui-b2-productivity

Conversation

@OBenner

@OBenner OBenner commented Jul 24, 2026

Copy link
Copy Markdown
Owner

Summary

Third B2 slice, and the first to prove the batch payoff: it reuses the generic AnalyticsDashboard from #439 with no new libs/ui component — just new mappers.

Electron

  • Pure productivity-ui mappers: formatHours; buildProductivityKpis / buildProductivityCharts / buildProductivitySections from ProductivitySummary + ProductivityTrendPoint, reusing analytics-ui's formatPercent/shortDate/sampleLabels/successRateTone (DRY). Backend success rates are 0.0–1.0, converted to whole percents. 7 tests.
  • ProductivityPilotView over getProductivitySummary + getProductivityTrends, mounted as "Productivity (new UI)" beside the legacy view.

i18n

  • analytics:productivityPilot.* (en+fr — the productivity screens share the analytics namespace), navigation:items.productivityNext.

Scope

The Productivity mockup's categorical bar panels ("when you ship" = hour-of-day, "where the time went" = category) have no backing data in ProductivitySummary/ProductivityTrendPoint. So — consistent with the Patterns pilot — this maps only the real data: KPI summary figures + the daily trend series as line charts + outcome/effort summary cards. No BarChart primitive is invented to render panels the backend can't fill; if that data lands later, a BarChart primitive + those panels are a clean follow-up.

Verification

Next in B2

Merge Analytics, then Model Usage (line/sparkline-based, fits the primitives directly).

🤖 Generated with Claude Code

Third B2 slice — the first to reuse the generic AnalyticsDashboard
from #439 with no new libs/ui component:

- Electron: pure productivity-ui mappers (formatHours; buildProductivity
  Kpis/Charts/Sections from ProductivitySummary + ProductivityTrend
  Point, reusing analytics-ui's formatters/shortDate/sampleLabels/
  successRateTone; converts the backend 0-1 rates to whole percents;
  7 tests) + ProductivityPilotView over getProductivitySummary +
  getProductivityTrends. Mounted as "Productivity (new UI)".
- i18n: analytics:productivityPilot.* keys (en+fr; the productivity
  screens share the analytics namespace), navigation.productivityNext.

Scope: the productivity mockup's categorical bar panels ("when you
ship", "where the time went") have no backing data in the report, so —
like the Patterns pilot — this maps only the real data: KPI summary
figures + the daily trend series as line charts + outcome/effort cards.
No BarChart primitive is invented for panels the backend can't fill.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@cursor

cursor Bot commented Jul 24, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@OBenner, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 2a29ddb8-9811-4c8c-93e6-57143ba98452

📥 Commits

Reviewing files that changed from the base of the PR and between f9d80fd and 62d330b.

📒 Files selected for processing (9)
  • apps/frontend/src/renderer/App.tsx
  • apps/frontend/src/renderer/__tests__/productivity-ui.test.ts
  • apps/frontend/src/renderer/components/ProductivityPilotView.tsx
  • apps/frontend/src/renderer/components/Sidebar.tsx
  • apps/frontend/src/renderer/lib/productivity-ui.ts
  • apps/frontend/src/shared/i18n/locales/en/analytics.json
  • apps/frontend/src/shared/i18n/locales/en/navigation.json
  • apps/frontend/src/shared/i18n/locales/fr/analytics.json
  • apps/frontend/src/shared/i18n/locales/fr/navigation.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/ui-b2-productivity

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@OBenner
OBenner merged commit c7b6219 into develop Jul 24, 2026
19 checks passed
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant