Skip to content
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

DPL-370 Labware destruction UX improvements [C=M] #365

Open
4 tasks
KatyTaylor opened this issue May 11, 2022 · 0 comments
Open
4 tasks

DPL-370 Labware destruction UX improvements [C=M] #365

KatyTaylor opened this issue May 11, 2022 · 0 comments
Labels
Could've MoSCoW Prioritization - Could/Good to Have Capability/Feature Enhancement New feature or request Labware Destruction

Comments

@KatyTaylor
Copy link
Contributor

KatyTaylor commented May 11, 2022

User story
There were a number of UX improvements requested during UAT of the labware destruction feature #338

I have grouped them together in this story as each of them is probably quite small, and it might help to think about them together.

Who are the primary contacts for this story
Katy, Danni

Acceptance criteria
To be considered successful the solution must allow:

  • Source labware box lines are numbered (easier for user to review the list before submitting)
  • Display errors / feedback messages for different labware in more user-friendly format (currently difficult to read if multiple labware are scanned in one go, as all errors appear on the same line)
  • Show confirmations for the labware successfully destroyed. (currently only failures are shown and it makes it hard to know what was successful)
  • Retain the list of labware that were scanned on-screen once you press submit. (easier for user to review the list and check they did the right thing -- ideally the list would use colours and icons to indicate which were successful and which failed to be destroyed)

N.B. It would be good if these can be implemented generically for all Asset Audits actions - UX improvements for everyone! There's nothing specific to the labware destruction feature here, as far as I know.

References
See the other stories with the 'labware destruction' label.

@KatyTaylor KatyTaylor changed the title DPL-nnn Labware destruction UX improvements DPL-nnn Labware destruction UX improvements [C=M,V=3] May 11, 2022
@KatyTaylor KatyTaylor changed the title DPL-nnn Labware destruction UX improvements [C=M,V=3] DPL-370 Labware destruction UX improvements [C=M,V=3] May 11, 2022
@SujitDey2022 SujitDey2022 removed the Enhancement New feature or request label Jul 4, 2023
@SujitDey2022 SujitDey2022 added the Could've MoSCoW Prioritization - Could/Good to Have Capability/Feature label Aug 22, 2023
@SujitDey2022 SujitDey2022 changed the title DPL-370 Labware destruction UX improvements [C=M,V=3] DPL-370 Labware destruction UX improvements [C=M] Sep 4, 2023
@SujitDey2022 SujitDey2022 added the Enhancement New feature or request label Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Could've MoSCoW Prioritization - Could/Good to Have Capability/Feature Enhancement New feature or request Labware Destruction
Projects
None yet
Development

No branches or pull requests

2 participants