You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug was found while testing #383. When version ID is != 1, and the user clicks on Continue action in the Reports page, then they will get an error which will not allow them to continue with the reporting.
Probability:
(How likely the bug is to happen, scored from 1-5. For example, probability of 5 is something like "it happens to all users every time they log in." whereas probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Impact:
(How bad the bug is when it does happen, scored from 1-5. For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected." whereas effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Log in as internal user
Navigate to Submit Annual Report(s)
Start a report for an operation (Bugle SFO - Registered can be used)
Finish the report throughout
Open the report again by clicking Continue
Change Report Type (the fields will be blanked out after changing Report Type)
Go back to the Reports page
Click Continue action on the specific operation
Workaround: change the version ID in the url to the latest one
Describe the Bug:
This bug was found while testing #383. When version ID is != 1, and the user clicks on
Continue
action in the Reports page, then they will get an error which will not allow them to continue with the reporting.Probability:
(How likely the bug is to happen, scored from 1-5. For example, probability of 5 is something like "it happens to all users every time they log in." whereas probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Impact:
(How bad the bug is when it does happen, scored from 1-5. For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected." whereas effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Submit Annual Report(s)
Continue
Continue
action on the specific operationWorkaround: change the version ID in the url to the latest one
Screenshots:
See page 40 of this document.
Additional information:
OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]
Additional Context
The text was updated successfully, but these errors were encountered: