...
- UI options for "save" button | meeting with UX/UI designers and Stripes team members to agree on a way forward (Gill Osguthorpe Kimie Kester Zak Burke )
- Mock-ups by Gill
- Responsive text fields
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4431 MCL: export complete lists
- is a Spike created?
- are there possible ways from a technical perspective to export full MCL list to excel?
- possibly create a Spike if not yet existing
- further MCL agreements: UI / UX agreements across apps → if no tickets existing → Martina will create them
...
UI options for "save" button
Mock-ups by Gill
Results
A | 1st question - pattern - single choice
B | 1st question - pattern - after adding the alternative choices from the comments section
C | 2nd question - options to change primary Save button
D | Comments
Lref gdrive file url https://docs.google.com/spreadsheets/d/1WhI-J6hZKiDuB-vgfcvPSjjgc8h1nt_Wewu_Lqm47jE/edit?usp=sharing
Requirements
| Requirements | Notes |
|---|---|
| A keyboard shortcut for each save function should be implemented as well. Perhaps ctr+alt+R for save and close (release record from editing)? | |
| Save & keep editing: record should stay in edit mode, | |
| Save & keep editing: no long loading times | |
| Save & keep editing: editing should continue where the user "left" the record | |
Responsive text fields
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4431
Next steps
Chat
Attendees
...