8000 Stepped Tracker previous steps as links · Issue #1868 · jpmorganchase/salt-ds · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Stepped Tracker previous steps as links #1868

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joshwooding opened this issue Jun 20, 2023 · 10 comments
Open

Stepped Tracker previous steps as links #1868

joshwooding opened this issue Jun 20, 2023 · 10 comments
Labels
component: stepped tracker status: waiting for 👍 Waiting for upvotes to gauge interest

Comments

@joshwooding
Copy link
Contributor
### Checklist
- [ ] Density (HD, MD, LD, TD)
- [ ] Mode (Light, Dark)
- [ ] Fill (Primary, Secondary, Tertiary)
- [ ] State (Default, Hover, Selected/Active, Disabled, Read-only, Other)
- [ ] Controlled API
- [ ] UITK accessibility parity (screen reader + keyboard interactions)
### Deliverables
- [ ] Characteristics spec
- [ ] Interactions spec, where necessary
- [ ] In Code & Figma (Component + Guide)
- [ ] Supporting site documentation
### Features
- [ ] Previous step navigation (New, optional, completed steps as links)
@mark-tate
Copy link
Contributor

@ivan-calderon @tomhazledine @jake-costa
this is a value add opportunity compared to our old component, is this possible in the new component technically, do the docs tell folks how to do it and is there any accessibility concerns ?

@mark-tate
Copy link
Contributor

Latte Goal: @jake-costa review any accessibility concerns, docs review by @ivan-calderon

@jake-costa
Copy link
Contributor

A11y comments added to Stepped Tracker Figma Specs. @ivan-calderon Ready for review

@mark-tate
Copy link
Contributor

Lungo Goal: No dev capacity

@mark-tate
Copy link
Contributor

Macc Goal:
QA Kris updates, push a copy to James for approval
Decision on Core sprint/date by EOS

@bhoppers2008
Copy link
Contributor

To be scheduled after feedback on Stepped Tracker labs release. Pushing back to backlog.

@mike-gray-pxd
Copy link
mike-gray-pxd commented Feb 20, 2025

The Stepped Tracker is being used in the Salt Migration pf Trade Processing Systems - image exported from Figma is included - also included is the an exported image of the existing TPS system that is built in Google Web Toolkit and has all the characteristics of an old Windows Application.

Critique from Ops representative Saiprasad Nimale on current system:

" No free navigation for Maker, Maker required to click Next button to travel to next screen - 15 screens required to be travers by clicking Next button only."

@chrispcode - FYI - you seemed interested in the 'why' and use case yesterday - user commentary above.
(I think I gave as many thumbs up as possible!)

@mike-gray-pxd
Copy link

(Couldn't upload images so linking to Confluence page with them on)

Images here

@bhoppers2008
Copy link
Contributor

Spoke with @mike-gray-pxd who will provide some more detailed requirements and edge cases for forward/back navigation within the stepper.

@mike-gray-pxd
Copy link

Hi @bhoppers2008 - I added some notes to the images in the Confluence page above.

"Transaction processing is a '4 eyes' process where a maker's work is checked by a 'checker'.
The transactions have between 15-20 steps.
In the current windows based UI (above right) they're horizontal tabs.
In the proposed Salt update (above left) it's the stepped tracker.

For both roles - but particularly the checker role - there is an operational need to navigate the steps non-linearly.
Clicking 'next' 15 times to get from 1 to 15 isn't desirable or operationally efficient."

(link to comment and images)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: stepped tracker status: waiting for 👍 Waiting for upvotes to gauge interest
Projects
Development

No branches or pull requests

6 participants
0