Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add/tracks events for my jetpack product card action button dropdown #37292

Conversation

CodeyGuyDylan
Copy link
Contributor

Proposed changes:

  • Add tracks events for My Jetpack product card action button dropdown
  • Fixed issue where chevron was not closing dropdown, only opening it
  • Fixed typo with with the connection banner

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Slack: p1714642553738749-slack-C06CVN9QVFY

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

Yes, we are adding tracks for the dropdown button for backups

Testing instructions:

  1. Checkout this branch via the Jetpack Beta plugin or your local dev environment
  2. Purchase VaultPress Backup for your site
  3. Wait for a backup to happen and then add an image or audio file or something to trigger an activity action that can be undone
  4. Go to /wp-admin/admin.php?page=my-jetpack and confirm you can see the dropdown (Screenshot doesn't have activity log item because I was forcing it visible in testing)
    image
  5. Open the dropdown and confirm you see the following event in Tracks Vigilante
    image
  6. Try closing it with the Chevron or by clicking outside of it and confirm you see a tracks event like this
    image
  7. Select the items inside of it and confirm you see tracks events for this
    image
    image
  8. Make sure opening the dropdown and closing it works as expected
  9. If you want, connect your site from the banner and make sure Connected is spelled correctly

Copy link
Contributor

github-actions bot commented May 8, 2024

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 WordPress.com Simple 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, and enable the add/tracks-events-for-my-jetpack-product-card-action-button-dropdown branch.

  • To test on Simple, run the following command on your sandbox:

    bin/jetpack-downloader test jetpack add/tracks-events-for-my-jetpack-product-card-action-button-dropdown
    

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

Copy link
Contributor

github-actions bot commented May 8, 2024

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 Team 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 🤖


The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.


Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

@github-actions github-actions bot added the [Status] Needs Author Reply We would need you to make some changes or provide some more details about your PR. Thank you! label May 8, 2024
@CodeyGuyDylan CodeyGuyDylan force-pushed the add/tracks-events-for-my-jetpack-product-card-action-button-dropdown branch from 30281ed to fd525e8 Compare May 8, 2024 19:39
Copy link
Contributor

@IanRamosC IanRamosC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code looks mostly fine, but I couldn't get the events to be recorded.
I also left a minor comment about the naming convention we use for Tracks events

@@ -202,9 +205,17 @@ const ActionButton = ( {
[ additionalActions, getStatusAction, hasAdditionalActions ]
);

const recordDropdownStateChange = useCallback( () => {
recordEvent( 'jetpack_myjetpack_product_card_dropdown_toggled', {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency, we tend to use the verb at the end in infinitive form. See more about that here

@@ -235,6 +250,11 @@ const ActionButton = ( {
const onDropdownMenuItemClick = () => {
setCurrentAction( allActions[ index ] );
setIsDropdownOpen( false );

recordEvent( 'jetpack_myjetpack_product_card_dropdown_action_clicked', {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

Suggested change
recordEvent( 'jetpack_myjetpack_product_card_dropdown_action_clicked', {
recordEvent( 'jetpack_myjetpack_product_card_dropdown_action_click', {

@@ -202,9 +205,17 @@ const ActionButton = ( {
[ additionalActions, getStatusAction, hasAdditionalActions ]
);

const recordDropdownStateChange = useCallback( () => {
recordEvent( 'jetpack_myjetpack_product_card_dropdown_toggled', {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
recordEvent( 'jetpack_myjetpack_product_card_dropdown_toggled', {
recordEvent( 'jetpack_myjetpack_product_card_dropdown_toggle', {

@CodeyGuyDylan CodeyGuyDylan force-pushed the add/tracks-events-for-my-jetpack-product-card-action-button-dropdown branch from b6bf1bc to 893ce22 Compare May 14, 2024 15:39
IanRamosC
IanRamosC previously approved these changes May 14, 2024
Copy link
Contributor

@IanRamosC IanRamosC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good and tests well. :shipit:

@IanRamosC IanRamosC added [Status] Ready to Merge Go ahead, you can push that green button! and removed [Status] Needs Author Reply We would need you to make some changes or provide some more details about your PR. Thank you! labels May 14, 2024
@CodeyGuyDylan CodeyGuyDylan merged commit 4064692 into trunk May 14, 2024
70 checks passed
@CodeyGuyDylan CodeyGuyDylan deleted the add/tracks-events-for-my-jetpack-product-card-action-button-dropdown branch May 14, 2024 17:15
@github-actions github-actions bot removed the [Status] Ready to Merge Go ahead, you can push that green button! label May 14, 2024
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.

None yet

2 participants