Angular Form Field Order
Bug #1857351 reported by
Terran McCanna
This bug affects 12 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.5 |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
In 3.4:
The pop-up forms that are used by the new Angular interfaces list the form fields alphabetically rather than in any sort of logical order. We are currently testing for our January upgrade and have received numerous confused complaints from staff who need to use those forms.
Examples: Carousel Editor, Address Alerts, Hold Policies, Shelving Locations Editor, etc.
Changed in evergreen: | |
status: | New → Confirmed |
tags: | added: angular |
Changed in evergreen: | |
assignee: | Jane Sandberg (sandbej) → nobody |
tags: | added: pullrequest |
Changed in evergreen: | |
milestone: | none → 3.5.1 |
Changed in evergreen: | |
importance: | Undecided → Medium |
Changed in evergreen: | |
milestone: | 3.5.1 → 3.5.2 |
tags: | added: signed |
tags: |
added: signedoff removed: signed |
Changed in evergreen: | |
milestone: | 3.5.2 → 3.next |
Changed in evergreen: | |
milestone: | 3.next → 3.6.1 |
Changed in evergreen: | |
milestone: | 3.6.1 → 3.6.2 |
Changed in evergreen: | |
assignee: | nobody → Jane Sandberg (sandbej) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note as of 3.4, the fm-editor component has a fieldOrder input. For these autogenerated UI's, we'll have to propagate the field order down to the fm-editor, likely via route data.