Don't consider user lifecycle status when repeating evaluation

[robertsreberski]

• Don't consider user lifecycle status when repeating evaluation
• changelog

Fixes #

Proposed changes:

• Show evaluation survey on "Redo" regardless user lifecycle status

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

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

Testing instructions:

• Follow the instructions from here (My Jetpack: add A/B experiment to welcome flow #38664) to get the treatment version
• Finish the evaluation, when you get recommendations
• Install and/or purchase new plugin to not be considered a new user
• Click context menu (three dots) and select "Redo" from the menu
• You should see evaluation survey again

[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 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 fix/welcome-flow-redo branch.

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

  bin/jetpack-downloader test jetpack fix/welcome-flow-redo
  

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 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.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[CodeyGuyDylan]

I followed the instructions and I am still seeing this issue 🤔

welcome-flow-issue.mov

[robertsreberski]

Hah! I was testing on local environment, where I disabled A/B experiment code. The thing is, issue is actually caused by experiment code 😅 This commit should finally deal with the issue.

It's still quite important to fix since we might consider running further A/B experiments relating to evaluation step (p1724799299091499/1724668117.451269-slack-C02LK1W8T4Z)

[CodeyGuyDylan]

Seems to fix the issue, thanks!