web client: item status batch edit fails to save if required stat cats have differing values

Bug #1738893 reported by Andrea Neiman
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
3.0
Fix Released
Medium
Unassigned

Bug Description

Per Beth Willis's comment here:

https://bugs.launchpad.net/evergreen/+bug/1691861/comments/4

"Our consortium requires values for statistical categories be entered in order to save a copy. When I select multiple copies to edit and the values for these attributes differ, no values display and I am unable to save the copies. It would not be unusual to batch edit a number of copies that do not share values for one or more statistical categories. In that case, it would be impossible to edit and save them all at once. I have attached a screenshot for illustration."

Marking confirmed as I see this behavior in current master running Cesar's patch for bug 1691861. I also see this behavior in the batch item editor for Copy Buckets, on a server without the patch for 1691861.

My testing shows that this is only an issue when stat cats are required.

Revision history for this message
Andrea Neiman (aneiman) wrote :

Edited title from "Bug" to its more descriptive current form.

Thanks bshum for tipping me off!

summary: - Bug
+ web client: item status batch edit fails to save if required stat cats
+ have differing values
Revision history for this message
Andrea Neiman (aneiman) wrote :

MassLNC has contracted Equinox to address this bug.

The fix will allow items with required stat cats to be saved if (a) required stat cat values are unchanged or (b) required stat cat values are changed to be the same value. This work will not address any additional copy editor interface display issues.

Revision history for this message
Cesar V (cesardv) wrote :
Cesar V (cesardv)
tags: added: pullrequest
Revision history for this message
Kathy Lussier (klussier) wrote :

Works for me! I signed off on the commit and merged it to release 3.0 and 3.1. Since the maintenance release notes were already done, I also added entries for this fix.

Changed in evergreen:
status: Confirmed → Fix Committed
milestone: none → 3.1.2
importance: Undecided → Medium
Changed in evergreen:
status: Fix Committed → Fix Released
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.