cfpb / sbl-project

Project management repo for the SBL project
Creative Commons Zero v1.0 Universal
1 stars 1 forks source link

[Story] Save point of contact information #149

Open angelcardoz opened 7 months ago

angelcardoz commented 7 months ago

Epic

Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.

[Epic] Provide point of contact https://github.com/cfpb/sbl-project/issues/150

User story

As a filer, I want to save my point of contact information, so that my POC is associated with my filing.

Acceptance criteria

Given [some context or conditions], when [the action that is performed], then [the expected observable outcome or behavior].

Technical tasks

Developers should create technical tasks and add links (below) prior to sprint planning.

Front end

Back end

natalia-fitzgerald commented 7 months ago

@dan-padgett @angelcardoz In order to avoid using "submit" to mean multiple things I was starting to think about alternatives to "Submit and continue". Would "Save and continue" make sense generally for our steps?

dan-padgett commented 7 months ago

I'm good with that change @natalia-fitzgerald. And then it sounds like we're trying to reserve "submit" for completing a task (e.g. submitting a request to update your profile) and using "save" otherwise?

natalia-fitzgerald commented 7 months ago

@angelcardoz I discussed with the devs and there's consensus that the contents of this story can be moved into the acceptance criteria for this story. This will keep consistency with the other epics and stories we've already written. Sound good?

natalia-fitzgerald commented 3 days ago

@angelcardoz Do you want to go ahead and move this story to the acceptance criteria for issue #147? If yes I can handle that OR if not, have we completed this story and if YES can we check this off in the epic and close this story?