3.5.0 Release Candidate Bugs

Bug	Cause	Solution	Priority? (Blocker or not?)	Remarks	Status	Reported By

Bug	Cause	Solution	Priority? (Blocker or not?)	Remarks	Status	Reported By
Active link highlighting is broken in the Patient Chart’s left navigation menu	The link highlighting logic in the `DashboardExtension` component in the styleguide needs to be augmented to properly account for URL segments.	https://github.com/openmrs/openmrs-esm-core/pull/1443 https://github.com/openmrs/openmrs-esm-core/pull/1445 https://github.com/openmrs/openmrs-esm-core/pull/1446	Must	Should be fixed in next RC cut	fixed	@Dennis Kigen
Queue transition validation timing can leave system in inconsistent state when target queue has existing patient entry	When transitioning a queue entry to a queue where the patient already has an active entry, the system can end up in an inconsistent state due to validation timing. The transition partially succeeds (ending the original entry) but then fails when trying to create the new entry, leaving the patient without any active queue entries in the target queue.	https://github.com/openmrs/openmrs-esm-patient-management/pull/1944 https://github.com/openmrs/openmrs-module-queue/commit/4dd38879c77fd8c6193914b65e7e4e5e0dc5529e	Must	Should be fixed in next RC cut	fixed	@Veronica Muthee
Some modules have unresolved backend dependencies error toast pops up when you land on the home page	We’ve included two frontend modules (`@openmrs/esm-billing-app` and `@openmrs/esm-stock-management-app`) in the RC that are not production ready and are still using older versions of the framework and common library.	Those two modules should be omitted from the `spa-assemble-config.json` file in the RC branch	Must	Should be fixed in next RC cut	fixed	@Veronica Muthee / @Olara Moses
Visits Issues - Cannot end active, Unable to start a visit while on tablet - 403 error issue	Likely related to frontend modules in Patient Management running on older versions of the framework and common lib at the time of publishing the RC.	https://github.com/openmrs/openmrs-esm-patient-management/pull/1899	Blocker	Should be fixed in next RC cut	FIXED	@Veronica Muthee
Start visit (tablet) Error 403 (under upcoming appointments)	Likely related to frontend modules in Patient Management running on older versions of the framework and common lib at the time of publishing the RC.	https://github.com/openmrs/openmrs-esm-patient-management/pull/1899		Should be fixed in next RC cut	fixed	@Veronica Muthee
Lab test results - unscrollable page - cannot enter the test results in a tablet			Should	Cannot reproduce this issue on my tablet. Re-tested on coffee break call. Still couldn’t reproduce the issue.	CAN'T REPRO	@Veronica Muthee
The system sometimes flags today’s vaccination date as invalid with the error: “Vaccination date cannot be in the future.”	Likely due to timezone validation issues between the server time and the user’s timezone. The date should be normalized to properly account for timezone differences.	https://github.com/openmrs/openmrs-esm-patient-chart/pull/2683	Must	Should be fixed in next RC cut	fixed	@Veronica Muthee
The Mental Health Assessment Form PHQ score should be automatically calculated.	PHQ-9 score is obtained by computing the total score from each of the fields in the form: Not at all = 0 Several days = 1 More than half the days = 2 Nearly every day = 3	The form schema should be amended to support auto-calculating the `Total score` field based on the provided answers if that is the desired goal.	Could	The `Total score` field is not backed by a calculateExpression or any other kind of automatic computation. If that was the intention, we should modify the form schema accordingly	pending	@Veronica Muthee
Uncaught type error (appears inconsistently … on a simulated tablet)			Could	Cannot reproduce this issue on my tablet. Re-tested on coffee break call. Still couldn’t reproduce the issue.	CAN'T REPRO	@Veronica Muthee
On the prescription form, the dose field has a default value of zero (0). When a user starts typing, the entered value is appended after the zero instead of replacing it, and the zero cannot be deleted, unless you move the cursor before the value first ……	The `dosage`, `pillsDispensed`, and `numRefills` fields all default to 0. These should be changed to default to `null` instead. Additionally, the Carbon `NumberInput` component that renders these fields in the form should be tweaked to allow empty strings as valid values so the field-level validation doesn’t kick in before the user types into the field.	https://github.com/openmrs/openmrs-esm-patient-chart/pull/2682	Should	Should be fixed in next RC cut	FIXED	@Grace Potma
In the dispensing app, if the "Dispense Prescription" button is clicked without entering a quantity, the form saves without any prompt or validation. What is expected is …. The system should validate that the quantity field is filled before saving. If it’s empty, it should display an error message (e.g., "Quantity is required to dispense") and block submission until the field is completed.	The value of the `quantity` field’s `NumberInput` in the form is hardcoded to 0. That’s why it always renders 0 instead of the actual user input that gets submitted in the payload. That should be changed to always show `medicationDispense.quantity.value` instead.	https://github.com/openmrs/openmrs-esm-dispensing-app/pull/431	Must	Should be fixed in next RC cut	Fixed	@Veronica Muthee
https://openmrs.atlassian.net/browse/O3-4780	The backend is likely returning the same test results in multiple concept trees and the frontend is faithfully processing all of them without deduplication. Additionally, as a follow up to whatever fix is proposed, we should extend the `obstree` resource to include the `obsUuid` in the response. This should make obs deduplication trivial per @Ian Bacher.	https://github.com/openmrs/openmrs-esm-patient-chart/pull/2701	Must	@Juliet Wamalwa Is there a chance this change can make it into the current release? It’s a high-priority fix for PIH if it’s close to being finished.”	fixed	@Fiona Anderson
https://openmrs.atlassian.net/browse/O3-4987	The visit history table data is not being invalidated when adding a medication via the order basket. We should add cache invalidation logic to the order basket submission logic.	https://github.com/openmrs/openmrs-esm-patient-chart/pull/2697	Should	Should be fixed in next RC cut	fixed	@Fiona Anderson
https://openmrs.atlassian.net/browse/O3-4988			Blocker	Can’t reproduce this issue	CAN'T REPRO	@Fiona Anderson
Creating a visit with a punctuality visit attribute fails with a 500 error code			Blocker	Can’t reproduce this issue on dev3 after the latest reset. Might it have been a metadata issue?	CAN'T REPRO	@Veronica Muthee
https://openmrs.atlassian.net/browse/O3-4986	Left nav menu is wrongly positioned for RTL locales.	https://github.com/openmrs/openmrs-esm-patient-management/pull/1941	Must	Should be fixed in next RC cut	fixed	@nethmi
https://openmrs.atlassian.net/browse/O3-4989	The logic doesn’t properly handle type property mapping from `cohort.cohortType?.display` on null values. We should update the code to handle those cases.	https://github.com/openmrs/openmrs-esm-patient-chart/pull/2695	Must	Should be fixed in next RC cut	fixed	@Fiona Anderson
https://openmrs.atlassian.net/browse/O3-5007	The Start Visit button in the advanced patient search calling `launchWorkspace()` from the patient chart app to launch the Visit form, but that fails silently because patient search doesn’t have a `WorkspaceContainer` registered in which to render the workspace.	https://github.com/openmrs/openmrs-esm-patient-management/pull/1958	Must	Should be fixed in next RC cut	fixed	@Juliet Wamalwa
https://openmrs.atlassian.net/browse/O3-4985	When attempting to transition, we get a 500 error on DuplicateQueueEntryException. I think the root cause is that the `isDuplicate()` check added here always returns true because it checks for overlap against any existing queue entry, and a transition (by definition) starts with an existing active queue entry, which overlaps with the new queue entry the transition attempts to create.	https://github.com/openmrs/openmrs-module-queue/pull/85	Blocker	Should be fixed in the next RC cut	fixed	@Chi Bong Ho
Queue entries don’t load for either the `doctor` or `nurse` user.	The Queue module has backend validation that checks for the `Get Queues` privilege before fetching queue entries. We need to extend the default role set to include that privilege. `{ "error": { "message": "User is logged in but doesn't have the relevant privilege [Privileges required: Get Queue Entries]", "code": "org.openmrs.aop.AuthorizationAdvice:120", } }`	https://github.com/openmrs/openmrs-content-referenceapplication-demo/pull/37	Must	Should be fixed in the next RC cut	fixed	@Juliet Wamalwa
https://openmrs.atlassian.net/browse/O3-5014	In the case of 'missed' appointments, the backend enforces default status change validation that prevents moving to lower sequence statuses except for Scheduled status. That means that if the user attempts to cancel a missed appointment, the `DefaultAppointmentStatusChangeValidator` throws an `APIException` with the specific error message: "Appointment status can not be changed from Missed to Cancelled". The appointment status sequence is defined as follows: Requested/WaitList: sequence 0 Scheduled: sequence 1 CheckedIn: sequence 2 Completed/Cancelled/Missed: sequence 3 The validation logic in `DefaultAppointmentStatusChangeValidator.validate()` prevents status changes where `toStatus.getSequence() <= currentStatus.getSequence()` unless the target status is `Scheduled`. Since both `Missed` and `Cancelled` have sequence 3, the validation fails and throws an `APIException` with the descriptive error message. However, the frontend is not properly catching and displaying this specific error message from the backend API exception, instead showing a generic error message to the user.	https://github.com/openmrs/openmrs-esm-patient-management/pull/1963	Should	Should be fixed in the next RC cut	fixed	@Juliet Wamalwa