New Circulation Duration Rule fields need to be put back in more user-friendly order

Bug #1839875 reported by Erica Rohlfs
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Committed
Medium
Unassigned
3.11
Fix Committed
Medium
Unassigned

Bug Description

Evergreen version 3.3

This bug is similar to bug https://bugs.launchpad.net/evergreen/+bug/1839874

Administration -> Server Administration -> Circulation Duration Rules -> click New Duration Rule button

In previous versions of Evergreen, when creating a new circ duration rule, the fields were displayed as name, max_renewals, shrt, normal, extended.

In 3.3 the order of the fields is: extended, id, max_renewals, name, normal, shrt, max_auto_renewals.

The order in 3.3 isn't entirely user-friendly. The duration fields for short (shrt), normal, and extended should be ordered together. max_renewals and max-auto_renewals should also be ordered together.

Revision history for this message
Bill Erickson (berick) wrote :

Depends on bug #1839881.

Revision history for this message
Felicia Beaudry (fbeaudry) wrote :

There was a fix committed for a relevant bug: https://bugs.launchpad.net/evergreen/+bug/1840050
You can now reorganize the columns with the column picker in 3.3 and 3.4, but it appears you will need to do it manually.

tags: added: admin-pages
removed: webstaffclient
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

This continues to be an issue in 3.9

The fields are not in a logical order on the pop-up when you create a new duration rule and the field names should be capitalized and use proper words.

I think the order should be:
Name
Short
Normal
Extended
Max Renewals
Max Auto Renewals

Changed in evergreen:
status: New → Confirmed
tags: added: usability
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Continues to be an issue in 3.11.1

tags: added: ux-forms webstaffcolumns
Revision history for this message
Terran McCanna (tmccanna) wrote :
tags: added: pullrequest
Changed in evergreen:
importance: Undecided → Medium
Revision history for this message
Jane Sandberg (sandbergja) wrote :

Thanks, Terran, and all who have commented on this bug. Pushed to rel_3_11 and above.

tags: added: signedoff
Changed in evergreen:
milestone: none → 3.12.4
status: Confirmed → Fix Committed
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.