Premium Analytics: offer the whole period menu on the post and video detail pages

[louwie17]

Fixes UNI-754

Proposed changes

The post and video detail pages offered five periods where the dashboard offered eleven. This gives them the same menu.

• The detail pages take the whole period menu. DETAIL_SURFACE_PRESETS is now the menu's own list plus all time, which a detail page can still anchor on the resource's publish date. The narrow list was drawn for the segmented pill row that Premium Analytics: add the date period dropdown #51835 / Premium Analytics: render the period dropdown in the date filters panel #51842 replaced with a dropdown, where the row's width bounded what could fit; a menu has no such bound, and the list was never revisited. Today and Yesterday have been on the dashboard menu since it landed.
• Custom range comes back. Premium Analytics: align the detail pages' date presets with the design #51533 dropped it because the pill row's mock had no room for it, and logged the removal as "easy to revisit — one-line flip". The dropdown's own design lists it, so withCustomRange: false goes.

A deep link naming a period the page did not offer, e.g. &preset=last-90-days, also stops falling back to a bare date range on the trigger — the period now names itself.

Screenshots

Post detail, period menu open:

Before	After

Related product discussion/links

• Linear: UNI-754
• The five-item list came from WOOA7S-1785 (Premium Analytics: align the detail pages' date presets with the design #51533); the dropdown that replaced the pill row came from WOOA7S-2025 (Premium Analytics: add the date period dropdown #51835, Premium Analytics: render the period dropdown in the date filters panel #51842).
• WOOA7S-1915 asked for Today and Yesterday from a customer interview and was closed as superseded by the WOOA7S-2025 design, not rejected.
• Month to date and Year to date, which the UNI-754 prototype also shows, are not here — they are not presets we ship on any surface yet. They are in Premium Analytics: add the Month to date and Year to date periods #52088, stacked on this branch, so this one stays scoped to the detail pages.

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

No.

Testing instructions

Build the dashboard: jetpack build --deps packages/premium-analytics, then open Premium Analytics (wp-admin/admin.php?page=jetpack-premium-analytics-wp-admin).

On a post's detail page (from Top posts) and a video's (from the VideoPress widget):

• Open the period dropdown. It lists Today · Yesterday · Last 24 hours · Last 7 days · Last 30 days · Last 90 days · Last 365 days · Last month · Last 12 months · Last year · All time · Custom range — the dashboard's own menu, with All time last and Custom range under it.
• Today and Yesterday resolve to that single day; the header reads "Performance from … to …" accordingly.
• Pick Custom range: the calendar opens beside the list, and Apply commits it.
• All time still starts on the post's publish / video's upload day, and still survives a reload.
• Load the page with &preset=last-90-days in the p param: the trigger reads "Last 90 days" rather than a date range.
• The dashboard is unchanged.

pnpm run test in projects/packages/premium-analytics passes (3175 tests), as does pnpm run test-tz.

🤖 Generated with Claude Code

https://claude.ai/code/session_015eDqAWndvFNBrBRdKcsYus

[github-actions]

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 add/uni-754-detail-date-presets branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/uni-754-detail-date-presets

bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/uni-754-detail-date-presets

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]

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!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: October 6, 2026

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Premium Analytics plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[retrofox]

LGTM. Thanks, Lourens 🚢