UX Enhancements
(UXPROD-856)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q4 2019 | Parent: | UX Enhancements |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Khalilah Gambrell | Assignee: | Khalilah Gambrell |
| Resolution: | Done | Votes: | 0 |
| Labels: | mcl, split, stripes-force, swag, ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||
| Epic Link: | UX Enhancements | ||||||||||||||||||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||
| Front End Estimator: | Cate Boerema (Inactive) | ||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | CB: Per discussion with the cap planning team and Jakub, some of us non-developers are estimating the remaining unestimated features so as not to disrupt development. I will tag this as "swag" so we know to come back to the estimate when we get closer to development. If, in the meantime, someone wants to improve my estimate, please feel free to do so, but ping me on Slack as a heads up so I can get it updated in the cap plan, as well.
This feature will create a wrapper for MCL - <ResultsList> that will give the user controls for visible columns and a few other aspects. A major feature is the ability to switch data-layouts based on some criteria (here: Pane-width used to switch between a cards vs multi-column layout) |
||||||||||||||||||||||||||||
| Development Team: | Stripes Force | ||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R2 | ||||||||||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||||||||||||||||||
| Rank: Leipzig (Full TBD): | R2 | ||||||||||||||||||||||||||||
| Rank: Leipzig (ERM Aut 2019): | R4 | ||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R4 | ||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||||||
| Description |
|
Multi-column list (MCL) component is used is nearly all FOLIO apps. Q3 2019 updates support improved user experience by:
|
| Comments |
| Comment by John Coburn [ 25/May/18 ] |
|
A portion of UX prod - passing the Pane's width down through context will be necessary for getting layouts to switch as we'd like them to. |
| Comment by Cate Boerema (Inactive) [ 05/Jun/18 ] |
|
Hi guys. I 'd like to keep the responsiveness features separate from the other usability features. Can we separate out the "which columns are visible, how is it sorted" (which seem like generally beneficial features) from "when does it switch between MCL and single col layout" (which is beneficial in the context of responsiveness)? |
| Comment by Cate Boerema (Inactive) [ 20/Sep/18 ] |
|
Changing dev team from Core to Frontside, as this is required by the capacity model. We will make sure the "frontside" team is given some of John C's time in the model. |
| Comment by Ann-Marie Breaux (Inactive) [ 03/Apr/19 ] |
|
Khalilah Gambrell There's a column picker component in fines/fees (
cc: Viktor Soroka |