Skip to content

Premium Analytics: remove the superseded Videos widget#50431

Draft
Nikschavan wants to merge 1 commit into
trunkfrom
remove/premium-analytics-videos-widget
Draft

Premium Analytics: remove the superseded Videos widget#50431
Nikschavan wants to merge 1 commit into
trunkfrom
remove/premium-analytics-videos-widget

Conversation

@Nikschavan

Copy link
Copy Markdown
Member

Proposed changes

The VideoPress widget covers the same Stats video-plays report as the older Videos widget, so there's no reason to keep both.

  • Remove the jpa/videos widget (renderer, data builder, stories, tests)
  • Point the default dashboard layout at jpa/videopress instead

Related product discussion/links

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

No.

Testing instructions

  • Build Premium Analytics and open the dashboard on a fresh site (or reset the saved layout so the default layout is regenerated)
  • Confirm the VideoPress widget renders in the slot the Videos widget used to occupy
  • Confirm the Videos widget no longer appears anywhere (default layout or when adding widgets)
  • Existing saved layouts that reference jpa/videos should simply drop that widget without errors

The VideoPress widget covers the same video-plays report, so drop the jpa/videos widget and point the default dashboard layout at jpa/videopress instead.
@github-actions

github-actions Bot commented Jul 11, 2026

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!

@github-actions github-actions Bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label Jul 11, 2026
@Nikschavan Nikschavan added [Status] Needs Review This PR is ready for review. and removed [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. labels Jul 11, 2026
@jp-launch-control

Copy link
Copy Markdown

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

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