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
Description & Context
Currently, QC and Long read teams communicate annotations and comments through emails or Slack. This creates inefficiencies when revisiting cells or checking sequencing outcomes. The ability to view annotations from the LR lab team directly would reduce communication overhead and allow the QC team to make informed decisions.
User Story
As a Data QC user, I want to view comments and annotations made by the LR team in LangQC so that I can make quicker and more accurate decisions without relying on back-and-forth communication.
Who are the primary contacts for this story @stevieing
Who is the nominated tester for UAT
LangQC and Lab teams
Acceptance criteria
To be considered successful the solution must allow:
QC users can view comments from the LR lab team in LangQC.
Comments include standard annotations such as "Low yield but passed as top up" or "Low p1% and yield possibly degraded DNA".
Annotations are stored in the system for later reference and linked to the appropriate cell or sequencing run.
The UI displays comments in a readable and accessible format.
Dependencies
This story is related to the following dependencies:
Description & Context
Currently, QC and Long read teams communicate annotations and comments through emails or Slack. This creates inefficiencies when revisiting cells or checking sequencing outcomes. The ability to view annotations from the LR lab team directly would reduce communication overhead and allow the QC team to make informed decisions.
User Story
As a Data QC user, I want to view comments and annotations made by the LR team in LangQC so that I can make quicker and more accurate decisions without relying on back-and-forth communication.
Who are the primary contacts for this story
@stevieing
Who is the nominated tester for UAT
LangQC and Lab teams
Acceptance criteria
To be considered successful the solution must allow:
Dependencies
This story is related to the following dependencies:
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: