My Jetpack: Send supported Modules links to Features

[LiamSarsfield]

Proposed changes

Open Features from supported Modules links, keeping search and tag selections. Keep Classic Modules for unsupported filters, offline sites and JavaScript or REST failures. Marked Features views include a Classic Modules list link. Keep the pinned footer and Reset action.

Related product discussion/links

Stacked on #53308. Keep this draft until the Features stack lands.

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

No new data. Migrated views wait for modules before recording the existing empty-state event.

Testing instructions

1. Connect a test site with Jetpack active. Follow Modules from My Jetpack’s footer, Help, the debugger and a Blog Stats block with Stats off. Expect Features; the Stats link selects Stats.
2. Open admin.php?page=jetpack_modules&s=stats&module_tag=Jetpack%20Stats. Expect both filters. Clear the tag, change the search, then follow Classic Modules list; it should match the current view.
3. Try module_tag=unknown, product_group=grow and activated=false. Expect Modules. Check Reload, Back and Forward.
4. Turn off JavaScript or REST, or return a REST authentication error. Settings and repointed links should reach usable Modules.
5. Enable Offline Mode, with the offline Features entry both on and off. Expect Modules.

Current Settings has no Modules footer item; AI’s unavailable-Features fallback stays classic.

Screenshots

Desktop 1440 unless marked mobile; test-site notices hidden.

Entry or view	Before	After
Modules menu
Settings footer
My Jetpack footer
Help link
Debugger
AI fallback
Blog Stats enable link
Saved search
Saved tag
Search and tag
Offline Modules menu
Mobile tag view (390)

[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 fm/mj-modules-redirect branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fm/mj-modules-redirect

bin/jetpack-downloader test jetpack-mu-wpcom-plugin fm/mj-modules-redirect

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.

[jp-launch-control]

Code Coverage Summary

No summary data is available for parent commit 66ee2ed, so cannot calculate coverage changes. 😴

If that commit is a feature branch rather than a trunk commit, this is expected. Otherwise, this should be updated once coverage for 66ee2ed is available.

Full summary · PHP report · JS report