-
Notifications
You must be signed in to change notification settings - Fork 34
Description
Context
A quality issue was raised due to tags not being added in manifests that require them. Missing tag information has caused downstream processing issues and significant rework. To prevent recurrence, the tag columns in any manifest requiring tags should be made mandatory and visually indicated. This will make it clear to Sample Users that tag fields must be completed before submission, ensuring data integrity and reducing process delays.
User story
As a Sample User, I want the tag columns in manifests that require tags to be clearly marked and mandatory, So that I am aware these fields must be filled in, and I can prevent errors and downstream processing issues caused by missing tag data.
Who are the primary contacts for this story
Lena H.
Who is the nominated tester for UAT
Lena H.
Acceptance criteria
Consider if these features can be featured flagged to decouple testing and deployment.
To be considered successful the solution must allow:
- The tag columns should be visually highlighted to indicate they are required to fill this information as it is important (make i5 and i7 fileds) [Orange colour!]
- Either a warning/info should display to inform users which tag fields need completion before submission, in Sequencescape or in the spreadsheet.
- Note: Confirm List of Manifest Types!
Dependencies
This story is blocked by the following dependencies:
- #<issue_no.>
- sanger/#<issue_no.>
References
This story has a non-blocking relationship with:
- #<issue_no.>
- sanger/#<issue_no.>
Additional context
make i5 and i7 fileds mandatory with the option of putting “n/a” in i5 column when the service user only needs one set of tags
Removed because we're not sure how we will know whether they need it or not.
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.