Skip to content

Premium Analytics: Fix posting activity heatmap range#50406

Draft
louwie17 wants to merge 2 commits into
trunkfrom
codex/fix-posting-activity-heat-map-pr
Draft

Premium Analytics: Fix posting activity heatmap range#50406
louwie17 wants to merge 2 commits into
trunkfrom
codex/fix-posting-activity-heat-map-pr

Conversation

@louwie17

@louwie17 louwie17 commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Fixes WOOA7S-1693

Proposed changes

  • Allow the shared calendar heatmap builder to respect explicit start/end bounds so sparse data no longer collapses the grid to the first/last active day.
  • Update the Posting Activity widget to query a trailing year ending at the dashboard date range end, then render the visible slice that fits the widget.
  • Use larger non-compact heatmap cells for larger tiles, while keeping compact rendering for tighter tiles.
  • Add high-relevance header arrow controls backed by an activityWindowOffset attribute so smaller visible windows can page through the trailing year.
  • Clamp the activity window at the latest and earliest pages so the header arrows disable at either end instead of wrapping.
  • Reset the activity window offset when the measured widget size changes, so resizing/customizing returns the heatmap to the latest window.
  • Add regression coverage for sparse posting activity, trailing-year bounds, size-aware paging, header arrow bounds, and resize resets.

Related product discussion/links

Does this pull request change what data or activity we track or use?

No.

Testing instructions

  • Run pnpm --dir projects/js-packages/charts test -- --runTestsByPath src/charts/heatmap-chart/test/build-calendar-data.test.ts.
  • Run pnpm --dir projects/js-packages/charts typecheck.
  • Run pnpm --dir projects/packages/premium-analytics test -- --runTestsByPath widgets/posting-activity/__tests__/posting-activity.test.tsx.
  • Run pnpm --dir projects/packages/premium-analytics typecheck.
  • Visual reference from a local sparse-response fixture:

Before and after posting activity heatmap

After posting activity heatmap

@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the codex/fix-posting-activity-heat-map-pr branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack codex/fix-posting-activity-heat-map-pr
bin/jetpack-downloader test jetpack-mu-wpcom-plugin codex/fix-posting-activity-heat-map-pr

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

@louwie17 louwie17 self-assigned this Jul 10, 2026
@jp-launch-control

jp-launch-control Bot commented Jul 10, 2026

Copy link
Copy Markdown

Code Coverage Summary

Coverage changed in 1 file.

File Coverage Δ% Δ Uncovered
projects/js-packages/charts/src/charts/heatmap-chart/private/build-calendar-data.ts 54/57 (94.74%) -1.34% 1 ❤️‍🩹

Full summary · PHP report · JS report

@louwie17 louwie17 force-pushed the codex/fix-posting-activity-heat-map-pr branch from 212a442 to d9e5ead Compare July 10, 2026 14:02
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