swongCO
commented
6 months ago UX Note Look into logic to detect if text is present in both fields. The other option is to add focus on either field to see if it'll enable the log in btn.
Time box some exploring if we can easily make the log in button recognize when text is entered in the fields or not. If it looks like an unreasonable amount of time, we will just have to add validation for the empty email and password fields.
Describe the Bug A clear and concise description of what the bug is. When a user saves their credentials in their browser, their email and password are pre-filled in to the email and password fields on the DAWSON log in page. If a user does this, the log in button is greyed out, and if you hover your mouse over the Log in button, there is a red circle with a slash through it. This makes it appear that the log in button is not working, even though it does work and the user can simply click it and they will log in.
We need to update this so that the button displays as active in this scenario, so as not to confuse users.
Business Impact/Reason for Severity Low
In which environment did you see this bug? Prod/Test
Who were you logged in as? I was not logged in. This happens on the log in screen
What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.) Using the system
To Reproduce Steps to reproduce the behavior:
Expected Behavior A clear and concise description of what you expected to happen. Log in button appears active
Actual Behavior A clear and concise description of what actually happened.
Log in button appears inactive, even though it can be clicked
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Cause of Bug, If Known
Process for Logging a Bug:
Severity Definition:
Critical Defect Blocks entire system's or module’s functionality No workarounds available Testing cannot proceed further without bug being fixed.
High-severity Defect Affects key functionality of an application There's a workaround, but not obvious or easy App behaves in a way that is strongly different from the one stated in the requirements
Medium-severity Defect A minor function does not behave in a way stated in the requirements. Workaround is available and easy
Low-severity Defect Mostly related to an application’s UI Doesn't need a workaround, because it doesn't impact functionality
Definition of Ready for Bugs(Created 10-4-21)
Definition used: A failure or flaw in the system which produces an incorrect or undesired result that deviates from the expected result or behavior. (Note: Expected results are use cases that have been documented in past user stories as acceptance criteria and test cases, and do not include strange behavior unrelated to use cases.)
The following criteria must be met in order for the development team to begin work on the bug.
The bug must:
Process: If the unexpected results are new use cases that have been identified, but not yet built, new acceptance criteria and test cases should be captured in a new user story and prioritized by the product owner.
If the Court is not able to reproduce the bug, add the “Unable to reproduce” tag. This will provide visibility into the type of support that may be needed by the Court. In the event that the Court cannot reproduce the bug, the Court will work with Flexion to communicate what type of troubleshooting help may be needed.
Definition of Done (Updated 4-14-21)
Product Owner
Engineering
testenvironment if prod-like data is required. Otherwise, deployed to anyexperimentalenvironment for review.