UNI-832: Premium Analytics: Open the dashboard from the admin bar and action bar Stats links

[Nikschavan]

Fixes UNI-832

Proposed changes

• Sites that turn on Stats v2 still land on classic Stats from most entry points. Premium Analytics: point the post list views column at the post detail page #51357 moved the post list Views column to the post detail page, but the admin bar sparkline, the admin bar "Stats" link, the post stats link in the newsletter action bar, and the My Jetpack redirect on Atomic Personal and Premium plans still open admin.php?page=stats.
• Each of those links now goes through a new jetpack_stats_url filter, with an array( 'view' => …, 'id' => … ) argument that names the page the link opens rather than the surface it sits on, with the same keys as the JS AnalyticsView in _inc/shared/analytics-url.ts. Stats_Links in Premium Analytics hooks it and maps dashboard to the dashboard root and post to /post/<id>. Any other view, a post view without a post ID, or a user without the view_analytics capability keeps the classic URL.
• Premium Analytics hooks the filter only while the dashboard is enabled, so turning v2 off sends every link back to classic Stats with no extra check at the call sites. A site that runs an older copy of one of the packages keeps the classic link for that one surface.
• The action bar in this repository runs only on Simple, and it is the only copy of the bar there since 240435-ghe-Automattic/wpcom removed the mu-plugin one. Its post stats link therefore opens the post detail page on Simple sites with Stats v2 on as soon as this deploys, winning over the Calypso post stats link the same way the post list column does.
• Post_List_Link keeps its name and public methods and now delegates to Stats_Links, so the post list column behaves as before.
• The sparkline image itself is still served from page=stats; only the link target changes.
• The Odyssey config also sends the site's timezone. The WP Admin dashboard widget, which comes from the Odyssey bundle built in Calypso, links into the dashboard on date ranges in UNI-832: Stats: Open Premium Analytics from the WP Admin dashboard widget wp-calypso#114767 and needs the timezone to keep whole days across daylight-saving changes, which gmt_offset alone cannot. It is empty for a site set to a fixed UTC offset.
• Not included: the admin bar sparkline on Simple sites comes from WordPress.com, so it changes in 245785-ghe-Automattic/wpcom.

Where the links are
The views sparkline in the admin bar, and "Stats" in the site-name menu (front end).

Related product discussion/links

• p1790600757879819-slack-C06FSDTSN82
• 245785-ghe-Automattic/wpcom passes the Simple admin bar sparkline through the same filter.
• UNI-832: Stats: Open Premium Analytics from the Hosting Overview, plan card and Customer Home stats links wp-calypso#114763 points the my.wordpress.com omnibar sparkline at the dashboard.
• UNI-832: Stats: Open Premium Analytics from the Hosting Overview and Customer Home stats links wp-calypso#114764 does the same for the Hosting Overview and Customer Home links.
• UNI-832: Stats: Open Premium Analytics from the WP Admin dashboard widget wp-calypso#114767 does the same for the WP Admin dashboard widget.
• UNI-832
• Premium Analytics: point the post list views column at the post detail page #51357

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

No.

Testing instructions

Self-hosted and Atomic. Use a Jurassic Ninja site with this branch through the Jetpack Beta Tester plugin, with Jetpack connected and the Stats module active. Turn Stats v2 on with wp option update jetpack_premium_analytics_enabled 1. Keep the standalone Premium Analytics plugin inactive: it turns the dashboard on unconditionally, so the option has no effect while it runs.

• Enable the admin bar chart in Jetpack › Settings › Traffic › Jetpack Stats if it is off.
• Open the front end. Click the views sparkline in the admin bar, and confirm it opens the Premium Analytics dashboard (?page=jetpack-premium-analytics-wp-admin).
• Hover the site name in the admin bar, click "Stats", and confirm it opens the same dashboard.
• On the posts list, click a post's Views count and confirm it still opens that post's detail page.
• Run wp option update jetpack_premium_analytics_enabled 0, reload, and confirm all three links open classic Stats (?page=stats) again.
• On an Atomic site with this branch, logged in as a WordPress.com user, hover the site name in the admin bar and confirm "Stats" opens the dashboard.
• On an Atomic site on a Personal or Premium plan, open wp-admin/admin.php?page=my-jetpack and confirm it redirects to the dashboard.

Simple. Sandbox a Simple site that has Stats v2 on, through its own opt-in or the jetpack-premium-analytics sticker. Then put this branch's builds on your sandbox by running both of these from the wpcom root: the jetpack build carries Premium Analytics, which hooks the filter, and the jetpack-mu-wpcom-plugin build carries the site-name "Stats" item.

bin/jetpack-downloader test jetpack 52905
bin/jetpack-downloader test jetpack-mu-wpcom-plugin 52905

• Open the front end, hover the site name in the admin bar, click "Stats", and confirm it opens admin.php?page=jetpack-premium-analytics-wp-admin&p=%2F.
• Open a published post on the front end and click the Stats button in the action bar. Confirm it opens the dashboard's post detail page (p=%2Fpost%2F<id>).
• The admin bar sparkline on Simple changes in 245785-ghe-Automattic/wpcom. To see it as well, check out that branch on the sandbox too.
• When you are done, run bin/jetpack-downloader reset jetpack and bin/jetpack-downloader reset jetpack-mu-wpcom-plugin.

I checked this with PHP unit tests only. I have not clicked through the links on a site with this branch yet, and the WordPress.com site menu only renders on WordPress.com sites. Action_Bar_Test covers the action bar link.

[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 uni-832-point-stats-entry-points-to-v2-for-opted-in-sites branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack uni-832-point-stats-entry-points-to-v2-for-opted-in-sites

bin/jetpack-downloader test jetpack-mu-wpcom-plugin uni-832-point-stats-entry-points-to-v2-for-opted-in-sites

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:

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.

---

Wpcomsh plugin:

• Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2)

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

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[jp-launch-control]

Code Coverage Summary

Coverage changed in 4 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/stats-admin/src/class-admin-bar.php	102/115 (88.70%)	0.10%	0 💚
projects/packages/stats-admin/src/class-admin-post-list-column.php	116/136 (85.29%)	0.92%	0 💚
projects/packages/stats-admin/src/class-odyssey-config-data.php	129/131 (98.47%)	0.01%	0 💚
projects/packages/newsletter/src/class-action-bar.php	374/632 (59.18%)	10.70%	-63 💚

1 file is newly checked for coverage.

File	Coverage
projects/packages/premium-analytics/src/class-stats-links.php	14/14 (100.00%) 💚

Full summary · PHP report · JS report

[fushar]

Please check this comment: Automattic/wp-calypso#114763 (review)

[chihsuan]

Nice work moving the Stats links over! @Nikschavan I tested the admin bar links, Views column and the Simple action bar with v2 on, and they work nicely. Approving. 👍

Before this merges, could we add changelog entries to plugins/jetpack and plugins/wpcomsh, since their users see these links change? I also left two inline notes.

[chihsuan]

Thanks, LGTM!