Batch Actions: issues with basket actions

Bug #1788485 reported by Andrea Neiman on 2018-08-22
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Medium
Unassigned
3.2
Undecided
Unassigned

Bug Description

From within the basket:

--add to existing list is misbehaving & erroneously reporting "empty basket"
--copying the following from Kathy Lussier's testing notes:

The "remove from basket" option doesn't always work as expected. If it's the first option I select from the cart, then it works fine. However, if I select the option to place a hold or email, return to the cart, and then select the option to remove from basket, it will bring me to the next step for placing a batch hold or sending an email, depending on what my previous action had been.

Galen Charlton (gmc) wrote :

A patch is available at the tip of the user/gmcharlt/lp1788485_improve_basket_action_redirects branch:

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

Changed in evergreen:
milestone: none → 3.2-beta
importance: Undecided → Medium
status: New → Confirmed
tags: added: pullrequest
Changed in evergreen:
milestone: 3.2-beta → 3.2-rc
Kathy Lussier (klussier) wrote :

Thank you Galen! Add to existing list is working as expected now. I am also able to perform multiple actions in the basket and then remove the titles without the strange behavior I previously reported.

However, I see one remaining issue when removing the titles. If I go to the basket and remove the titles as my first action, the catalog removes those titles and returns me to whatever page I was on before going to the basket.

If I email the titles, for example, and then return to the basket to remove the remaining titles, I stay on the basket page with a message the says "basket is empty" with a Return button that brings them nowhere. I'm guessing that, at this point, the catalog no longer remembers where the user was before they first accessed the basket. Is there a way that this original page can be remembered? If not, could we have a default page to return to when that button is clicked?

Changed in evergreen:
milestone: 3.2-rc → 3.2.1
Changed in evergreen:
milestone: 3.2.1 → 3.2.2
Changed in evergreen:
milestone: 3.2.2 → 3.2.3
Changed in evergreen:
milestone: 3.2.3 → 3.3-beta1
Changed in evergreen:
milestone: 3.3-beta1 → 3.3-rc
Changed in evergreen:
milestone: 3.3-rc → 3.3.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers