Open angelcardoz opened 4 months ago
For the User Story, the main aim of the warning is to convey what happens when the user replaces the file. The file summary and the button text changing to something like "Replace file" should be enough to convey that there's already a file in the system. One way of rephrasing the last part of the story is: "so that I understand the new file will be associated with the filing instead of the old one, and that I will no longer be able to access the validation report for the current file".
@natalia-fitzgerald does my suggestion match how you understand what happens when a user replaces their file?
replace second half of the story with "so that I understand the new file will replace the old one".
Epic
Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.
User story
Acceptance criteria
Technical tasks
Developers should create technical tasks and add links (below) prior to sprint planning.
Front end
Back end