Open anwyss opened 4 years ago
Hey Anna
thanks for going in much more detail on this! Does it make sense to keep two different boards though? I'm sure we track all issues (technical and overall) in https://github.com/orgs/re-CoV-er/projects/1? If you want more columns (review etc.), we can add them.
for us it fits well to have a board with the technical slices. meaning, we take your issues and split them into these technical slices without all the business noise. This slice I added is lets say a "sub-slice" of your USM: Authentication - Signup & Login #11
OK for now. I'll create links between the respective issues(/PRs).
GOAL Registered users can login
ACCEPTANCE CRITERIA
TECHNICAL NOTES
login
to the filegraphql/authentication
authenticationEpic
tosignupEpic
and rename fileredux/epics/login
for login parallel to signupEpic. It should send the querylogIn
with variablesemail
andpassword
and map response to the actionLOG_IN_SUCCESS
orLOG_IN_FAILURE
login
in fileredux/action-creators
that creates an action that has the type LOG_IN and the payloademail
andpassword
.LOG_IN_SUCCESS
LOG_IN_FAILURE
authentication
with caseLOG_IN
,LOG_IN_SUCCESS
andLOG_IN_FAILURE