Events Listing: Using Past events or custom date range filters for dates in the past shows duplicate event recurrences

[jilladams]

Describe the defect

Listing: Using Past events or custom date range filters for dates in the past shows duplicate event recurrences

e.g. https://www.va.gov/minneapolis-health-care/events/?endDateDay=19&endDateMonth=06&endDateYear=2022&selectedOption=custom-date-range&startDateDay=13&startDateMonth=06&startDateYear=2022

e.g. https://www.va.gov/minneapolis-health-care/events/?endDateDay=14&endDateMonth=06&endDateYear=2022&selectedOption=custom-date-range&startDateDay=08&startDateMonth=06&startDateYear=2022

To Reproduce

Steps to reproduce the behavior:

• Go to Outreach & Events listing, or a VAMC Event listing page (currently only seeing recurrences on VAMC events listings), e.g. https://www.va.gov/minneapolis-health-care/events/
• Custom date range: enter at least one date in the past, or filter by Past events
• See that events will appear with the same Title / date / time.
• Cross-check with the CMS node for that event, and see only a single instance of that event date / time, e.g. https://prod.cms.va.gov/minneapolis-health-care/events/42754

Expected behavior

Past events or date filters showing past events should only show each recurrence one time.

Screenshots

Additional context

This example can be a little confusing, as the MN editors have worked around a recurrence limitation by creating 2 of the same events, with weekly recurrences on different days (Mon vs. Wed).

• Mon recurrence = https://prod.cms.va.gov/minneapolis-health-care/events/42754
• Thurs recurrence = https://prod.cms.va.gov/minneapolis-health-care/events/46932

You can test this in Staging for a more clear cut example of what happens for events with recurrences in the past, when using filters.

Labels

(You can delete this section once it's complete)

• [x] Issue type (red) (defaults to "Defect")
• [ ] CMS subsystem (green)
• [ ] CMS practice area (blue)
• [x] CMS workstream (orange) (not needed for bug tickets)
• [ ] CMS-supported product (black)

CMS Team

Please check the team(s) that will do this work.

• [ ] Program
• [ ] Platform CMS Team
• [ ] Sitewide Crew
• [ ] ⭐️ Sitewide CMS
• [X] ⭐️ Public Websites
• [ ] ⭐️ Facilities
• [ ] ⭐️ User support

[jilladams]

Per Dave review in S61 planning, low priority.

[jilladams]

This may also be resolved by #9456

[jilladams]

This was not resolved by #9456 Repro: https://www.va.gov/central-iowa-health-care/events/?selectedOption=past

Moving to stretch / next sprint as an option for FE people to pick up who are looking for work.

[maxx1128]

@jilladams I'm checking this locally and it's resolved for me. Is it possible the fix wasn't fully pushed to production?

[jilladams]

Yep, correct -- just confirmed and I had tested right before deploy completed. No longer repros for me - thanks for verifying! Sorry for churn. CLosing.