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

MNTOR-3953 - Add monthly report free email state for expired sub #5668

Merged
merged 1 commit into from
Feb 27, 2025

Conversation

codemist
Copy link
Collaborator

References:

Jira: MNTOR-3953
Figma:

Description

The "auto-removed" table should not be 0 if a user had previously auto-removed data exposures but then downgraded to a free account.

Screenshot (if applicable)

image

Not applicable.

How to test

Checklist (Definition of Done)

  • Localization strings (if needed) have been added.
  • Commits in this PR are minimal and have descriptive commit messages.
  • I've added or updated the relevant sections in readme and/or code comments
  • I've added a unit test to test for potential regressions of this bug.
  • If this PR implements a feature flag or experimentation, I've checked that it still works with the flag both on, and with the flag off.
  • If this PR implements a feature flag or experimentation, the Ship Behind Feature Flag status in Jira has been set
  • Product Owner accepted the User Story (demo of functionality completed) or waived the privilege.
  • All acceptance criteria are met.
  • Jira ticket has been updated (if needed) to match changes made during the development process.
  • Jira ticket has been updated (if needed) with suggestions for QA when this PR is deployed to stage.

@codemist codemist requested review from flozia and Vinnl February 26, 2025 18:42
Copy link

// If a free scan is run, show auto-removed exposures (should be 0, unless a user has an expired sub with previously removed exposures)
dataPointValue: hasRunFreeScan
? props.dataSummary.dataBrokerAutoFixedDataPointsNum
: 1,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Question: Is showing the auto-removed exposures as 1 when no scan has been run correct here: Wouldn’t there be no exposures that could have been removed?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Ah, I see: In this scenario, without a used free scan we don’t show the auto-removed exposures here, but the number of available scans.
image

// If a free scan is run, show auto-removed exposures (should be 0, unless a user has an expired sub with previously removed exposures)
dataPointValue: hasRunFreeScan
? props.dataSummary.dataBrokerAutoFixedDataPointsNum
: 1,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Ah, I see: In this scenario, without a used free scan we don’t show the auto-removed exposures here, but the number of available scans.
image

@codemist codemist merged commit c7d7490 into main Feb 27, 2025
16 checks passed
@codemist codemist deleted the mntor-3953 branch February 27, 2025 15:30
Copy link

Cleanup completed - database 'blurts-server-pr-5668' destroyed, cloud run service 'blurts-server-pr-5668' destroyed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants