Copy Alert count not adjusted properly after clearance on Holdings View

Bug #1798628 reported by tji@sitka.bclibraries.ca
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
3.2
Fix Released
Medium
Unassigned

Bug Description

EG 3.1.4

Find an example copy with a copy alert

Go to Holdings View > Edit Copies, click Copy Alerts, select Clear checkbox. OK, Save & Exit.

Back on Holdings View, the count in Alerts column remains the same. Clearing caches, refreshing the screen. The number persists.

Add another copy alert via Copy Edit. Back on HOldings View, the alert count increases.

If repeating this process, the alert count keeps increasing though you may have one alert only.

Tina Ji

BC Libraries Coop

Revision history for this message
John Amundson (jamundson) wrote :

I am seeing this, as well.

I have an item with only 1 copy alert, but the count in Holdings View reads "12". The count does not seem to be taking into account alerts that have been cleared/acknowledged.

tags: added: webstaffclient webstaffcolumns
Changed in evergreen:
status: New → Confirmed
Revision history for this message
Jason Boyer (jboyer) wrote :

Here's a branch that changes how the copy alerts are counted in the holdings view. This should prevent any confusion where the column claims there are X alerts but clicking the Manage button displays between 0 and X actual alerts.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1798628_holdings_alert_count / working/user/jboyer/lp1798628_holdings_alert_count

tags: added: pullrequest
Revision history for this message
Garry Collum (gcollum) wrote :
tags: added: signedoff
Andrea Neiman (aneiman)
Changed in evergreen:
importance: Undecided → Medium
milestone: none → 3.3-rc
no longer affects: evergreen/3.0
Revision history for this message
Chris Sharp (chrissharp123) wrote :

Pushed to master and rel_3_2. Thanks, Jason and Garry!

Changed in evergreen:
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
no longer affects: evergreen/3.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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