Describe the Bug:
Reg\Register an Operation\Facility Information is missing default values for facility name & facility type
Reproduction steps:
Sign in as an industry user with access to an operator (example: 'bc-cas-dev' user)
Navigate to "Register an Operation"
In Operation Information\Select your operation field, select "Operation 3"
Complete required fields
Click 'Save and Continue'
Results:
Missing default values for facility name & facility type
[09/Oct/2024 15:48:05] "GET /api/registration/operations/3b5b95ea-2a1a-450d-8e2e-2e15feed96c9/facilities HTTP/1.1" 200 162
[{'type': 'uuid_parsing', 'loc': ('path', 'facility_id'), 'msg': 'Input should be a valid UUID, invalid length: expected length 32 for simple format, found 2', 'ctx': {'error': 'invalid length: expected length 32 for simple format, found 2'}}]
Possible resolution:
Correct fixture for valid UUID,
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."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (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."
Effect of 1 is "It makes some styling look a little bit weird.")
Describe the Bug: Reg\Register an Operation\Facility Information is missing default values for facility name & facility type
Reproduction steps:
Results: Missing default values for facility name & facility type
[09/Oct/2024 15:48:05] "GET /api/registration/operations/3b5b95ea-2a1a-450d-8e2e-2e15feed96c9/facilities HTTP/1.1" 200 162 [{'type': 'uuid_parsing', 'loc': ('path', 'facility_id'), 'msg': 'Input should be a valid UUID, invalid length: expected length 32 for simple format, found 2', 'ctx': {'error': 'invalid length: expected length 32 for simple format, found 2'}}]
Possible resolution:
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." Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (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." Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Screenshots:
Additional information: