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

GPL-480 Support Heron Lysed TubeRack purposes from SS #104

Open
emrojo opened this issue May 20, 2020 · 1 comment
Open

GPL-480 Support Heron Lysed TubeRack purposes from SS #104

emrojo opened this issue May 20, 2020 · 1 comment

Comments

@emrojo
Copy link

emrojo commented May 20, 2020

User story
GPL-480 As SRA for CGaP (Laura) I want to use Extraction Lims to accept the plate purpose Heron Lysed TubeRack for tube racks as an input from Sequencescape.

Who the primary contacts are for this story
Laura (CGaP)

Acceptance criteria
To be considered successful the solution must allow:

The user can scan the barcode from a Heron Lysed TubeRack rack
The rack is imported into Extraction lims

Additional context
As today 20th May, this story affects the plate purpose created at story GPL-478.

@emrojo emrojo added the enhancement New feature or request label May 20, 2020
@emrojo emrojo changed the title GPL-nnn Support Heron Lysate TubeRack purposes from SS GPL-nnn Support Heron Lysed TubeRack purposes from SS May 20, 2020
@emrojo
Copy link
Author

emrojo commented May 20, 2020

Tasks

  • Depending on result from GPL-476 (precondition) create a new TubeRack plate purpose in Sequencescape named Heron Lysed TubeRack with size 96.
  • Add a test to check everything behaves as expected in Extraction.

@rl15 rl15 changed the title GPL-nnn Support Heron Lysed TubeRack purposes from SS GPL-480 Support Heron Lysed TubeRack purposes from SS May 20, 2020
@rl15 rl15 added Heron Extraction and removed enhancement New feature or request labels May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants