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

Y24-489 - Show the robot button Bravo LCMT DNA Adp Lig => LCMT DNA Lib PCR after the WGS branch submission #2100

Open
4 tasks
yoldas opened this issue Dec 2, 2024 · 0 comments
Labels
Could've MoSCoW Prioritization - Could/Good to Have Capability/Feature EMSeq ToR 170 Enhancement New feature or request Size: M Medium - medium effort & risk

Comments

@yoldas
Copy link
Member

yoldas commented Dec 2, 2024

User story

As Limber user running LCM Triomics EMSeq and WGS pipeline, I would like the robot button Bravo LCMT DNA Adp Lig => LCMT DNA Lib PCR to be available after the WGS branch submission is done.

"After marking the LCMT DNA Adp Lig plate as passed using Manual Transfer, upon scanning the plate back into Limber the ‘WGS Branch – Automated Submission’ button becomes available as expected. However, the bed verification step ‘Bravo LCMT DNA Adp Lig => LCMT DNA Lib PCR’ is already exposed to the user before the submission has been made, which is potentially slightly confusing because this step is only required if the WGS branch is required (as the LCMT DNA Lib PCR plate does not exist before the button is clicked). However I do appreciate that it is also the case that the user only needs to scan the passed LCMT DNA Adp Lig plate back into Limber if the WGS branch is needed; otherwise the LCMT TET2 Ox plate becomes the next point of interaction with Limber and none of the above will be seen. I’m happy with the current arrangement, but if there is some simple way to ensure that the bed verification option is only visible after the WGS branch has been generated that would be useful."

Who are the primary contacts for this story
Scott G.
Abdullah

Who is the nominated tester for UAT
Scott G.

Acceptance criteria

To be considered successful the solution must allow:

  • The robot button Bravo LCMT DNA Adp Lig => LCMT DNA Lib PCR is shown after WGS branch is submitted.
  • The robot button respects the pipeline filters, similar to suggested child purposes.
  • The robot button is shown after the LCMT DNA Lib PCR plate is created.
  • Integration suite is updated to check the availability of the button.

Dependencies

This story is blocked by the following dependencies:
N/A

References
This story has a non-blocking relationship with:

Additional context
This may be implemented as a generic feature to make sure robot buttons are not rendered when they are not relevant. However, it aims to solve a specific UX issue of the LCM Triomics EMSeq and WGS pipeline.

The following screenshot shows that the Bravo LCMT DNA Adp Lig => LCMT DNA Lib PCR button is available even though WGS Branch - Automated Submissions is not done and the LCMT DNA Lib PCR plate is not added yet.

Screenshot 2024-12-02 at 15 45 41

@psd-issuer psd-issuer bot changed the title Show robot button Bravo LCMT DNA Adp Lig => LCMT DNA Lib PCR after the WGS branch submission Y24-489 - Show robot button Bravo LCMT DNA Adp Lig => LCMT DNA Lib PCR after the WGS branch submission Dec 2, 2024
@yoldas yoldas added the EMSeq ToR 170 label Dec 2, 2024
@yoldas yoldas changed the title Y24-489 - Show robot button Bravo LCMT DNA Adp Lig => LCMT DNA Lib PCR after the WGS branch submission Y24-489 - Show the robot button Bravo LCMT DNA Adp Lig => LCMT DNA Lib PCR after the WGS branch submission Dec 2, 2024
@yoldas yoldas added Could've MoSCoW Prioritization - Could/Good to Have Capability/Feature Size: M Medium - medium effort & risk Enhancement New feature or request labels Dec 2, 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 EMSeq ToR 170 Enhancement New feature or request Size: M Medium - medium effort & risk
Projects
None yet
Development

No branches or pull requests

1 participant