#7918525 Jetpack Backup: Add 2-day backup retention option on cancel plan page

PT: peaFOp-1b9-p2
Design: p1HpG7-lDY-p2

Proposed Changes

In order to reduce churn, due to the site reaching the storage limit, we’d like to experiment with showing the option to set the retention to two days in the cancelation flow for those customers that have reached their storage limit.

This change will offer customers an option to set 2-day retention on the plan cancellation page (for individual backup plans or any bundled plan having backup feature) and current retention set to higher than 2 days.

Testing Instructions

Before this change:

After this change (it will show a 2-day retention offer on the cancel page for limited storage backup plans):

The following cases should pass:

• It should not be visible for an unlimited storage plan.

• It should not be visible for plans with 2-day retention already set.

• It should not be visible if the plan being canceled does not have a BACKUP feature, some examples

  • Jetpack Search – on cancel it should not be visible
  • Any individual Jetpack Backup or bundled plan such as Jetpack Security that includes backup – on cancel page it should be visible

• It should be visible only if the site is over the storage limit.

  • To make a site over the storage limit for testing, we can update its backups_stopped site attribute to true from vpshell, e.g.

    vpshell > $site = get_site_by_id(1221683);
    vpshell > return $site->set_attribute( 'backups_stopped', true );
    1
    

    Note: The backups_stopped site attribute may get reset after the next daily backup if the site is not over the storage limit actually, in that case, we could again set the backups_stopped to true or make the site’s last backup size bigger than the limit by updating the <site-id>_vp_snapshot_info table’s size column (of the latest period row)

• Once 2-day retention is updated from the cancel page it should record a tracks event with 2-day retention (Similar to what we have on the Settings page)

• Once the updation is successful, it should redirect to the Settings page.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the “[Status] String Freeze” label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the “[Status] Needs Privacy Updates” label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?