search

dbsites / project-q

4 stars 6 forks source link

BUG: State does not update if one issue is selected and user clicks submit #44

Open joelkperkins opened 6 years ago

joelkperkins commented 6 years ago

DB write bug we observed with issues logged with no position appears to be due to the double submission of userIssues at the issueSelection screen.

User must click submit twice to update state and move through the application. However, each submit click creates a userIssue submission. [after logging in] 1

[after selecting one issue] 2

[after clicking submit once] 3

[after clicking submit twice] 4

I will investigate server response after the first click and see if that is the source of the error. If not, I will start trying to fix this on the back end, by enforcing no double insertions to userIssues (which needs to be an included functionality anyways)

However, UX-wise the submit button should move the user along.

joelkperkins commented 6 years ago

Back end side is fixed, the double storage of issues was an query error on my part. The query is fixed and values properly write.

It still takes two clicks to move past the issues survey I am thinking this could be because of the response object missing something, if it is a back end bug

joelkperkins commented 6 years ago

This is a back end error, response from first submit click is missing the issues the front end needs to move forward

joelkperkins commented 6 years ago

FIXED Issues resolved