Web Client - Archived Penalties/Messages does not Respect Date Range

Bug #1775940 reported by John Amundson
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
3.4
Fix Released
Medium
Unassigned

Bug Description

Evergreen Web Client 3.0.8

From the Messages tab in a patron's account, Archived Penalties/Messages are displayed for the last year by default. In theory, older messages can be retrieved via editing the date range. However altering the date range does not update the list.

For example, today is 6/8/2018. By default, archived messages created between 6/8/2017 and 6/8/2018 are displayed. No matter how I edit or change the date range, I only ever see the messages created between 6/8/2017 and 6/8/2018.

In the XUL client, there was a "Retrieve Archived Penalties" command that does not exist in the web client.

Garry Collum (gcollum)
Changed in evergreen:
status: New → Confirmed
Revision history for this message
Eva Cerninakova (ece) wrote :

Confirmed in Evergreen 3.3.2

Revision history for this message
a. bellenir (abellenir) wrote :
Changed in evergreen:
milestone: none → 3.5-alpha
Revision history for this message
Jason Stephenson (jstephenson) wrote :

We implemented the fix suggested by a.bellenir on our Evergreen 3.4 test server at CW MARS, and it fixes the issue for us. Below is a branch that implements this fix with signoffs:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dyrcona/lp1775940-watchQuery-fix

tags: added: pullrequest signedoff
Michele Morgan (mmorgan)
Changed in evergreen:
milestone: 3.5-beta → 3.5.0
Changed in evergreen:
milestone: 3.5.0 → 3.5.1
Revision history for this message
Galen Charlton (gmc) wrote :

Pushed all the way to rel_3_3. Thanks, Jason and John!

I note that if a user types in the date input, the Javascript console will log a bunch of errors of the form "TypeError: $scope.dates.start_date is undefined". This is noisy, but I'm letting that go for now since at first glance it looks like a fix for that would be a little tricky if we want to avoid refreshing the grid while one of the date inputs is in an invalid state.

Changed in evergreen:
importance: Undecided → Medium
status: Confirmed → Won't Fix
status: Won't Fix → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
Andrea Neiman (aneiman)
no longer affects: evergreen/3.3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.