Skip to content

Y26-129 - Prevent Accidental Overwriting of Volume and Concentration Data #5687

@Stan1520

Description

@Stan1520

Context
Currently, uploading a sample manifest automatically overwrites existing volume and concentration data, which can lead to accidental data loss and quality issues. Users need more control to prevent unintended overwrites.

User story
As a user, I want the option to choose whether volume and concentration data are overwritten during sample manifest upload, So that I can prevent accidental loss of important lab data.

Who are the primary contacts for this story
Steve W

Who is the nominated tester for UAT
Steve W

Acceptance criteria
To be considered successful the solution must allow:

  • The sample manifest upload page includes two separate checkboxes: one for “Overwrite Volume” and one for “Overwrite Concentration.”
  • Both checkboxes are unchecked by default.
  • When unchecked, existing volume and/or concentration data must remain unchanged after upload.
  • When checked, the system overwrites the respective data fields with values from the uploaded manifest.
  • When checked, the system should warn the user if a cell is left empty (and not affect the current value stored)
  • When volume or concentration data is overwritten by a manifest, a log entry in the application log is made indicating this has happened and who did it.

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
Value - "Quality log mitigation and prevents accidental overwriting of lab data."

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.

Metadata

Metadata

Assignees

Labels

EnhancementNew feature or requestSize: MMedium - medium effort & risk

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions