Open jeffsieu opened 2 years ago
Thank you for your suggestion. We will take that into consideration 😊.
Team chose [response.NotInScope
]
Reason for disagreement: This is a part of the application that every user has to go through, so it's a non-trivial bug. And it is unexpected behaviour (as a user myself, I expected the focus to be on the previous field). Hence it matches the specifications of a FunctionalityBug. I do not see why this should be out of the scope when it is a bug in the essential part of the application.
Issue
Entering an erroneous pair of passwords causes both fields to be cleared, but the focus to remain on the second field
Steps to reproduce
password
, then in the second fieldpassworf
.Expected behaviour
Since both fields are cleared, for the focus to re-focus on the first field.
Actual behaviour
The focus remains on the second field.
Screenshots
Bug severity justification
This is a rather annoying bug, as entering wrong passwords are common. However, this only happens during the set-up phase and is a one-time event, hence the severity is
VeryLow
.