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

Feature to duplicate seedlots from TPT, UPT and CUS #1551

Open
9 tasks
SLDonnelly opened this issue Aug 26, 2024 · 1 comment
Open
9 tasks

Feature to duplicate seedlots from TPT, UPT and CUS #1551

SLDonnelly opened this issue Aug 26, 2024 · 1 comment

Comments

@SLDonnelly
Copy link
Collaborator

SLDonnelly commented Aug 26, 2024

As a TSC Admin I want to be able to view and duplicate seedlots registration records from UPT and CUS seedlots So That I can duplicate them if they get returned

Acceptance Criteria

  • Given that a seedlot has a TPT, UPT or CUS source code , When I enter the affiliated seedlot number and click on a "duplicate seedlot" button, then the seedlot data is copied to a new registration form in pending status and given the next available number for the 62000 series.
  • Given that I have duplicated a seedlot, when I go to the collection information section, the volumes are set to 0.01 hl and the comment section includes a comment 'copied from 6xxxx'.
  • Given that I have duplicatd a seedlot, when I go to the ownership section, the fields are blank and ready for me to enter new ownership information.

Definition of Done

  • Ready to Demo in Sprint Review
  • Does what I have made have appropriate test coverage?
  • Documentation and/or scientific documentation exists and can be found
  • Peer Reviewed by 2 people on the team
  • Manual testing of all PRs in Dev and Prod
  • Merged
@SLDonnelly SLDonnelly changed the title Feature to duplicate seedlots from UPT and CUS Feature to duplicate seedlots from TPT, UPT and CUS Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants
@SLDonnelly and others