[UXPROD-4266] Receiving filter search results do not match "expected receipt date" period specified Created: 03/May/23  Updated: 30/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Aliaksandr_Lukashevich5 Assignee: Dennis Bridges
Resolution: Unresolved Votes: 0
Labels: known-issue-lotus, known-issue-morningglory, known-issue-nolana
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified
Environment:

https://bugfest-lotus.int.aws.folio.org/


Attachments: File expectedReceiptDateFilterBug.mp4    
Issue links:
Blocks
is blocked by RMB-953 SQL query generating incorrectly Closed
Duplicate
duplicates MODORDERS-791 Receiving filter search results do no... Closed
Relates
relates to FAT-3240 Review of C366536 Closed
Development Team: Thunderjet
PO Rank: 0
Solution Architect: Olamide Kolawole

 Description   

Overview:

Very likely another time zone of the back-end affects the accuracy of "expected receipt date" filter results when 7 hours difference overlaps midnight (bugs were found for expected receipt date after 5 p.m.). Also is typical for POL filter date-created field. The same issue

Preconditions: 

Logged onto FOLIO as a user with all permissions

Steps to Reproduce:

  1. I set the expected receipt date under Search & filter to 9/19/22. It's bringing up 126 records, but not all of the records contain pieces that show 9/19/22 as the expected receipt date. For example, in the screenshot you'll see that this title shows an expected receipt date of 12/15/22. The one piece that's already been received shows an expected receipt date of 11/17/21. We are working in eastern standard time.

Expected Results: results retrieved match filter criteria specified
Actual Results:

1. Receiving results include Title record with different "Expected receipt dates"

Additional Information:
URL:
Interested parties:



 Comments   
Comment by Dennis Bridges [ 03/May/23 ]

I have converted this issue to a feature because it will require the coordination of updates in multiple modules and should involve an architect

Generated at Fri Feb 09 00:38:32 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.