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

"Challenge" button should remain disabled until a project is selected #200

Open
nieldlr opened this issue Oct 26, 2020 · 0 comments · May be fixed by #201
Open

"Challenge" button should remain disabled until a project is selected #200

nieldlr opened this issue Oct 26, 2020 · 0 comments · May be fixed by #201

Comments

@nieldlr
Copy link

nieldlr commented Oct 26, 2020

Hiya team,

I found an error/bug in the validation as part of the Challenge flow.

When you go to challenge a project, you are asked to select a project. Initially I was unsure if I needed to select that & went straight to writing the reason for a challenge. The "Challenge" button then became enabled & I clicked it to go ahead with the challenge. I assumed with this flow the project field was not required.

Once you click the button, it shows the "Waiting for transaction" screen for short while & then the transaction/flow fails & resets without a reason why.

Perhaps it would be better to explain that the Project field is definitely required & also prevent the "Challenge" button from becoming enabled if that field is missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant