We need to add tests to the backend and frontend to cover the case(s) of a null appointment date time. Doing this may uncover a bug we also need to fix.
From the API team:
Good morning, we have resolved the null appointment date issue on our side. The appointmentDate field in the /claims endpoint can now potentially have a null value. I don't know if this would be a breaking change for you or not. Hopefully not
Risks
[ ] Adding these tests may uncover a bug we also need to fix, which may impact at least velocity and at most delivery
Description
We need to add tests to the backend and frontend to cover the case(s) of a null appointment date time. Doing this may uncover a bug we also need to fix.
From the API team:
Risks
Acceptance Criteria
Definition of Done
How to configure this issue