You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context
The Triomics pipeline currently supports only the combined EMseq/WGS workflow.
User story
As a user, I want the Triomics pipeline to include a WGS-only workflow branch, so that users can choose the appropriate workflow at the start of the process and trigger the correct downstream routing, plate creation, and sequencing submissions automatically.
Who are the primary contacts for this story
Scott G
Who is the nominated tester for UAT
Scott G
Acceptance criteria
To be considered successful the solution must allow:
A new WGS-only workflow branch must be defined in Limber.
Unique WGS-only plate types must be created and correctly linked to downstream steps.
Includes labware relationships and bed verifications defined in the following documents:
Add any details that should be noted when deploying this feature. For example, is a database migration needed, a specifc rake task or other script that needs to be run, a dependency on another application or service that needs to be released first etc?
These notes are intended to ensure the developers releasing the feature know what needs to be done.
Add any other context or screenshots about the feature request here.
Note
This story is a draft
Context
The Triomics pipeline currently supports only the combined EMseq/WGS workflow.
User story
As a user, I want the Triomics pipeline to include a WGS-only workflow branch, so that users can choose the appropriate workflow at the start of the process and trigger the correct downstream routing, plate creation, and sequencing submissions automatically.
Who are the primary contacts for this story
Scott G
Who is the nominated tester for UAT
Scott G
Acceptance criteria
To be considered successful the solution must allow:
Dependencies
This story is blocked by the following dependencies:
Additional context
Deployment notes
Add any details that should be noted when deploying this feature. For example, is a database migration needed, a specifc rake task or other script that needs to be run, a dependency on another application or service that needs to be released first etc?
These notes are intended to ensure the developers releasing the feature know what needs to be done.
Add any other context or screenshots about the feature request here.