Bucket grid configuration updates do not save
Bug #1805895 reported by
Anna Goben
This bug affects 19 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.1 |
Fix Released
|
Medium
|
Unassigned | ||
3.2 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Bucket views are all reverting to default grid configurations and are refusing to save any changes. This seems to be affecting all three types of buckets.
Examples:
-Record buckets: Remove the Record ID column. Save. Refresh. Record ID returns.
-Item buckets: Add Copy Status column. Save. Refresh. Copy Status disappears.
-User buckets: Add Preferred First Name column. Save. Refresh. Preferred First Name disappears.
Am attaching a screencast.
Evergreen 3.2.1
Changed in evergreen: | |
status: | New → Confirmed |
tags: | added: cataloging webstaffclient |
Changed in evergreen: | |
importance: | Undecided → Medium |
tags: | added: ws-settings |
Changed in evergreen: | |
assignee: | nobody → Jane Sandberg (sandbej) |
Changed in evergreen: | |
milestone: | none → 3.3.3 |
assignee: | Galen Charlton (gmc) → nobody |
Changed in evergreen: | |
assignee: | nobody → Jason Boyer (jboyer) |
Changed in evergreen: | |
assignee: | Jason Boyer (jboyer) → nobody |
Changed in evergreen: | |
status: | Confirmed → Fix Committed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
These grids appear to have correct persist-key settings, and they are included in the new server-side database settings. So perhaps there's a bug in the bucket apps somewhere.