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

PCIU Replacement Step 4a: Fix AddressValidation Bugs #98561

Closed
4 of 5 tasks
Tracked by #73776
RachalCassity opened this issue Dec 6, 2024 · 4 comments · Fixed by department-of-veterans-affairs/vets-api#19829
Closed
4 of 5 tasks
Tracked by #73776

Comments

@RachalCassity
Copy link
Member

RachalCassity commented Dec 6, 2024

User Story

As a developer, I want to fix AddressValiation, so that the Contact Information Service upgrade is complete.

Issue Description

The AddressValidation feature is encountering issues in the staging environment. These bugs are impacting functionality and causing unexpected behavior during the address verification process. This ticket is to identify, debug, and resolve these issues to ensure proper performance and reliability.

Tasks

  • Reproduce the issues locally to understand their root causes.
  • Implement necessary fixes in the AddressValidation logic or API integration.
  • Test thoroughly to confirm the resolution of the bugs.

Acceptance Criteria

@RachalCassity RachalCassity changed the title Fix AddressValidation Bugs PCIU Replacement Step 5: Fix AddressValidation Bugs Dec 6, 2024
@AshleyGuerrant AshleyGuerrant added backend 2024 bug Something isn't working labels Dec 6, 2024
@AshleyGuerrant
Copy link

AshleyGuerrant commented Dec 6, 2024

Sprint reporting note: This ticket needs to be injected into Sprint 16. This bug was identified as a part of the review process during Sprint 15 for this PR. Additional modifications to the epic workflow are being track in #98514.

@AshleyGuerrant AshleyGuerrant added unplanned-work Work that was not planned for during Sprint Planning post-planning and removed unplanned-work Work that was not planned for during Sprint Planning labels Dec 6, 2024
@AshleyGuerrant
Copy link

As mentioned in a Slack thread, this bug fix is in progress and I am updating the status.

@AshleyGuerrant
Copy link

Standup note: working on resolving some flaky tests, the PR should be up shortly.

@RachalCassity
Copy link
Member Author

Fixed two more bugs found during local testing. Waiting to test in staging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment