Angular form field order: Hold Policies
Bug #1915464 reported by
Michele Morgan
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.11 |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
A followup to bug 1857351 where the field order of many angular forms was addressed.
Further discussion was needed on the field order in the Hold Policies page. Given the large number of "cause and effect" type fields, it would be helpful to put some thought into a sensible order.
Suggestions from the initial report:
Hold Policies
This one has so many fields, I think it would be helpful to put the Description field first and then to break it up visually into natural groups of fields related to related to a) item, b) user, c) holds (or something along those lines).
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
assignee: | nobody → Terran McCanna (tmccanna) |
Changed in evergreen: | |
assignee: | nobody → Terran McCanna (tmccanna) |
Changed in evergreen: | |
milestone: | 3.12.4 → 3.12.5 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Proposed patch at: https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ mccanna/ lp1915464_ hold_policies_ field_order
I wasn't able to figure out a way to add visual breaks in the modal, but the new order is roughly
Description - Active - Owning & Circ Libs - Record & Item Info - User Info - Hold Info - Transit Info.