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

Staging Review finding: Blue Button form flow displays wrong dates after custom date range page #99395

Open
3 tasks
shiragoodman opened this issue Dec 18, 2024 · 1 comment

Comments

@shiragoodman
Copy link
Contributor

Need help? Please review how to read a Staging Review ticket. Tag @platform-governance-team-members on Slack if you need further assistance.

This ticket was part of a merged Staging Review with MHV Medical Records Download Records, Flow/Images and Settings

Product Information

Team: vfs-mhv-medical-records
Product: MHV Medical Records
Feature: Phase 1 Radiology Flow/Images, Download Records, and Settings

Findings details

VA.gov Experience Standard - issue: User experiences an unexpected interaction with a component or pattern.
VA.gov Experience Standard - category: Usability
Launch-blocking: No
Design System review: No
Collab Cycle Reviewer: @erinrwhite (IA)

Description

When entering a custom date range in the Blue Button form flow, the form asks for a start and end date for a custom report. On the next page to select record type, the form displays dates that are one day before the dates selected on the previous page. For example, selecting a custom range of "June 1, 2022-June 1, 2023" displays as "May 31st, 2022-May 31st, 2023" on the next page.

Link, screenshot or steps to recreate

incorrect date range

Recommended action

Update the displayed date to reflect the range selected by the user.

References

  • Accessibility Defect Severity: N/A
  • WCAG Success Criteria: N/A
  • Modality: N/A
  • Design System Component: N/A
  • Design System Pattern or Template: N/A
  • Design System Foundation: N/A
  • Content Style Guide: N/A
  • Context: N/A

Next Steps for the VFS Team

  • Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members with any questions or to get help validating the issue.
  • Ticket ownership: If you believe that this issue is out of scope, not your team's responsibility, or a Design System issue, comment and tag @platform-governance-team-members on your team channel in Slack to provide an explanation and who you believe is responsible. The Governance team will follow up.
  • Close this ticket when the issue has been resolved or validated by your Product Owner.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants