#3142: Domain Expiring Filter + CTA Banner - [RH]

[therealslimhsiehdy]

Ticket

Resolves #3142

Changes

• Domain renewal feature flag (see /admin)

For domain_renewal flag off:

• Should see no banner
• Should see no "Expiring soon" status in the Status column

If domain_renewal flag on:

• New filter by addition in the table (only for non org model)
• Call to action banner if the user has 1 domain

• Non org model Figma - the text is correct even though this is on org model
• Org model Figma

• Call to action banner if user has multiple domains

• Non org model Figma
• Org model Figma - the text is correct even though this is on non org model

• Call to action banner's link is clickable and click to update the status to "Expiring soon"

• Non org model Figma
• Org model Figma

• Domain Overview

• Non org model Figma

• Org model Figma for if domain manager

• Org model Figma if not domain manager

• In the Status column, if a domain is in "Expiring soon" state, make sure there is a red "!" by it

• If user does not have expiring domains, make sure call to action banner does not exist

Context for reviewers

For domains pending expiration (≤60 days from its expiration date), highlight the need to take action in the Domains dashboard.

Setup

1. Test without the domain_renewal flag on first
2. Test with only the domain_renewal flag on
3. Test with the domain_renewal flag on + now organization_feature flag on

Note: If you don't have domains that are expiring within 60 days

1. Go to the sr/registrar/fixtures/fixtures/fixtures_domains.py, and then to _generate_fake_expiration_date
2. Update the expiration date to a number between 1 and 60.
3. Run the following to load the fixtures:
   docker-compose exec app bash
./manage.py load
   must have domains in review for this to work

Code Review Verification Steps

As the original developer, I have

Satisfied acceptance criteria and met development standards

• Met the acceptance criteria, or will meet them in a subsequent PR
• Created/modified automated tests
• Update documentation in READMEs and/or onboarding guide

Ensured code standards are met (Original Developer)

• If any updated dependencies on Pipfile, also update dependencies in requirements.txt.
• Interactions with external systems are wrapped in try/except
• Error handling exists for unusual or missing values

Validated user-facing changes (if applicable)

• Tag @dotgov-designers in this PR's Reviewers for design review. If code is not user-facing, delete design reviewer checklist
• Verify new pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
• Checked keyboard navigability
• Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

As a code reviewer, I have

Reviewed, tested, and left feedback about the changes

• Pulled this branch locally and tested it
• Verified code meets all checks above. Address any checks that are not satisfied
• Reviewed this code and left comments. Indicate if comments must be addressed before code is merged
• Checked that all code is adequately covered by tests
• Verify migrations are valid and do not conflict with existing migrations

Validated user-facing changes as a developer

Note: Multiple code reviewers can share the checklists above, a second reviewer should not make a duplicate checklist. All checks should be checked before approving, even those labeled N/A.

• New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
• Checked keyboard navigability
• Meets all designs and user flows provided by design/product
• Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
• (Rarely needed) Tested as both an analyst and applicant user

As a designer reviewer, I have

Verified that the changes match the design intention

• Checked that the design translated visually
• Checked behavior. Comment any found issues or broken flows.
• Checked different states (empty, one, some, error)
• Checked for landmarks, page heading structure, and links

Validated user-facing changes as a designer

• Checked keyboard navigability
• Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
• Tested with multiple browsers (check off which ones were used)
  • Chrome
  • Microsoft Edge
  • FireFox
  • Safari
• (Rarely needed) Tested as both an analyst and applicant user

References

• Code review best practices

Screenshots

[github-actions]

🥳 Successfully deployed to developer sandbox rh.

[therealslimhsiehdy]

Created a new PR due to rebasing issue so it's cleaner.