UI Responsiveness
(UXPROD-828)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | UI Responsiveness |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Khalilah Gambrell | Assignee: | Khalilah Gambrell |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | stripes-force, technical, ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Epic Link: | UI Responsiveness | ||||||||||||
| Analysis Estimate: | Large < 10 days | ||||||||||||
| Analysis Estimator: | John Coburn | ||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||
| Front End Estimator: | John Coburn | ||||||||||||
| Estimation Notes and Assumptions: | We need to figure out a method for allowing developers to have control over which Pane renders in front when multiple Panes are present.
Possibilities: focus-based: using react's bubbling focus event, we could assign a Pane a high z-index when focus enters it. static priority: have developers assign a number to a Pane, highest number wins in stacking order (basically z-index) |
||||||||||||
| Development Team: | Stripes Force | ||||||||||||
| PO Rank: | 70 | ||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||
| 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: MO State (MVP June 2020): | R4 | ||||||||||||
| Description |
|
Work needed
|
| Comments |
| Comment by Cate Boerema (Inactive) [ 13/Sep/18 ] |
|
UXPROD feature assignee = product owner. I am assigning this to Khalilah for now, as she is the temporary PO for UX/stripes |
| Comment by Cate Boerema (Inactive) [ 20/Sep/18 ] |
|
Changing the dev team from Core to Frontside (this is needed by the cap plan model - we will make sure the "frontside" team in the model gets some of John Coburn's time. |
| Comment by Khalilah Gambrell [ 23/Oct/18 ] |
|
For Q4 2018 - we will work on defining user stories for implementation in future quarters. |
| Comment by Khalilah Gambrell [ 22/Jun/20 ] |
|
Hkaplanian and Cate Boerema, Stripes-force did implement a related feature, resizable panes. Is this feature still cap-mvp? |
| Comment by Cate Boerema (Inactive) [ 22/Jun/20 ] |
|
I'm honestly not sure how this came to be cap-mvp given it is ranked rather low. Also, I am wondering if there was confusion about what this feature represented. What would be the user impact of this change? The writeup is very dev-focused. Hkaplanian do you remember why this was cap-mvp? |
| Comment by Hkaplanian [ 22/Jun/20 ] |
|
This is very developer focused. I don't believe this was supposed to be included in the prioritization process. |