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-3378 - Data broker manual removal #5287

Open
wants to merge 29 commits into
base: main
Choose a base branch
from
Open

MNTOR-3378 - Data broker manual removal #5287

wants to merge 29 commits into from

Conversation

codemist
Copy link
Collaborator

@codemist codemist commented Nov 4, 2024

References:

Jira: MNTOR-3378
Figma: https://www.figma.com/design/DTbmXzCQCw2PxXpHQW8yfW/Monitor-MVP-Enhancements?node-id=3809-6501&t=EniBV7WqvPVnuivk-4

Path: /user/dashboard/fix/data-broker-profiles/removal-under-maintenance

Description

Screenshot (if applicable)

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

Copy link

github-actions bot commented Nov 4, 2024

Comment on lines +11 to +12
| "removed"
| "removal_under_maintenance";
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@rhelmer I believe this would be our first time consuming this endpoint for the manual data broker removal feature.

@codemist codemist requested a review from rhelmer November 4, 2024 19:20
Copy link

github-actions bot commented Nov 4, 2024

Copy link

github-actions bot commented Nov 4, 2024

Copy link

github-actions bot commented Nov 6, 2024

@codemist codemist marked this pull request as ready for review November 12, 2024 18:53
@codemist codemist added the 🛑 Do Not Merge Do not merge this PR, even if approved. label Nov 12, 2024
Copy link

Copy link

Copy link

Copy link

Copy link

Copy link

locales/en/exposure-card.ftl Outdated Show resolved Hide resolved
locales-pending/dashboard-premium.ftl Outdated Show resolved Hide resolved
Copy link
Collaborator

@flozia flozia left a comment

Choose a reason for hiding this comment

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

This is looking good so far! There are some open comments and questions I’m having:

  • Before landing any parts of this feature we’ll need to make sure to guard it behind a feature flag.
  • Additionally, we would need to add telemetry (potentially in a follow-up) to the CTAs to fulfill the acceptance criteria.
  • For smaller viewports it might be better to stack the buttons:
image

locales-pending/dashboard-premium.ftl Outdated Show resolved Hide resolved
locales-pending/dashboard-premium.ftl Outdated Show resolved Hide resolved
<div className={styles.removalContentSection}>
<dt>
{l10n.getString(
"data-broker-removal-maintenance-steps-to-remove-header",
Copy link
Collaborator

Choose a reason for hiding this comment

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

This header would need to be:

Suggested change
"data-broker-removal-maintenance-steps-to-remove-header",
"data-broker-removal-maintenance-rationale-header",

data={props.stepDeterminationData}
hideProgressIndicator={detailedRemovalGuide}
>
{!detailedRemovalGuide ? dataBrokerInformation : removalGuideInstructions}
Copy link
Collaborator

Choose a reason for hiding this comment

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

The only way to go back to the exposures when the “removal instructions” are open is by clicking “Back to exposures” (which for many viewport sizes is out of sight). I’m wondering if it would not be more intuitive to follow our existing pattern of showing explainers in dialogs. If that was already decided against by UX and/or is out of scope we should at least make sure that the closing “x” button does not link back to the dashboard.

image

@@ -85,6 +86,21 @@ describe("ScanResultCard", () => {
expect(innerDescription).toBeInTheDocument();
});

// Data broker removal under maintenance
it("shows the right description for a scan result card where removal is under maintenance", () => {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Nit: Should we also add a test that checks that the description is not shown for other statuses?

Copy link

2 similar comments
Copy link

Copy link

Copy link

Copy link

Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛑 Do Not Merge Do not merge this PR, even if approved.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants