Web Client: Sort Priority not honored in egGrid
Bug #1790169 reported by
Erica Rohlfs
This bug affects 13 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.1 |
Won't Fix
|
Medium
|
Unassigned | ||
3.2 |
Fix Released
|
Medium
|
Unassigned | ||
3.3 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Web Client version 3.0.9
When configuring columns in the Check In screen or the Capture Holds screen, the user can set a Sort priority. Once the user navigates away from the screen, the sort priority is no longer honored, and the user must reset the column priority.
To recreate, go into either the Check In screen or Capture Hold screen. Select the column picker drop-down option Configure Columns -> set a Sort priority on one of the columns -> go back into the column picker drop-down and select Save Columns. Navigate away from the screen (or simply refresh the screen), go back into the column configuration option and notice that the sort priority is no longer set.
tags: | added: sorting |
tags: | removed: sorting |
tags: | added: sorting |
tags: | added: pullrequest |
Changed in evergreen: | |
milestone: | none → 3.1.14 |
importance: | Undecided → Medium |
Changed in evergreen: | |
milestone: | 3.1.14 → 3.4-beta1 |
tags: | added: eg-grid |
tags: | added: signedoff |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I tested this extensively in 3.1.5 with spot checks in 3.1.4 and 3.0.9.
1) Pick a grid, any grid -- I looked at all of Circ & Cataloging in 3.1.5
2) Set a sort priority for various columns in Manage Columns (or Configure Columns, if in 3.0.x)
3) Click Actions Menu --> Save Columns
4) In 3.1.x, Sort priority is not saved or honored (problem #1), even though Manage Columns shows the sort value(s) that you entered. 3.0.x does seem to apply the sort order when you save it.
5) If you navigate away from the interface and then back, all sort values return to default & will show as 0 if looked at in Configure Columns (3.0.x) or Manage Columns (3.1.x) - Problem #2
Updating the title to reflect that this seems to be a larger problem.