Bug | Cause | Solution | Remarks | Priority? (Blocker or not?) | Status | Reported By | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Possibly: Because not using the standard Calendar Picker in the Registration page? | ? | Grace: We should release, but we will need a patch to fix this one promptly. | Blocker |
| Veronica & Grace | |||||||||||||||||||
Add config so new order types show: Imaging, Procedures. | the new order types can be added via Configuration. Currently, the refApp only supports 2 order types. Eg in Ozone: order types Imaging and Procedures are added via configuration | Nice-to-have; Not blocker |
| Grace | |||||||||||||||||||||
Photos do not render in patient chart Header on physical Tablet (ok on desktop and using dev tools | Ian was able to replicate the issue on test3 on his computer. then he was able to spot the issue in the devtools console. it’s an issue with how the REST module handles http requests. Ian’s aware and planning to work on a fix | Nice-to-have; Not blocker |
| Grace | Add config so new order types show: Imaging, Procedures. | the new order types can be added via Configuration. Currently, the refApp only supports 2 order types. Eg in Ozone: order types Imaging and Procedures are added via configuration | Nice-to-have; Not blocker | | Status | | ||||||||||||||||
| colour | Red | title | not started
Grace
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
This order is defined by the this configuration here. The Network calls how that the config is not being fetched by the server, and hence the order seems incorrect.
Nice-to-have; Not blocker
| Status | ||||
|---|---|---|---|---|
|
by Ian
Grace
Ward app visible in Home Left Nav
Same as row 1
Same as row 1
Fixed Blocker
| Status | ||||
|---|---|---|---|---|
|
Grace
Uncaught TypeError: (0 , i.getPatientChartStore) is not a functionwhen launching patient chart
This is because one of the frontend modules that have the dependency `patient-common-lib` is not up to date. It's most likely the billing module.
We have removed the billing module in this PR.
It's weird that we made a new patch release since the PR was made, and the deploy build has happened but the changes are not reflected in test3.
Fixed Blocker
| Status | ||||
|---|---|---|---|---|
|
Vero
The Billing Home App is unable to fetch data, resulting in a 404 error, and continuously making requests in an infinite loop in test3.
Same as row 2, its because the backend dependency kenyaemr is not present.
Same as row 1
Same as row 1
Fixed Blocker
| Status | ||||
|---|---|---|---|---|
|
Praneeth
Some modules have unresolved backend dependencies. Check the Backend Modules tab in the Implementer Tools for more detailsafter logging in
Because the billing module has a dependency which is “kenyaemr”
Same as above
Same as above
Fixed Blocker
| Status | ||||
|---|---|---|---|---|
|
Vero
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Lost the ability to scroll on a Tablet in test3, but it's fine in dev3
The re-release this Wednesday (3.3.0-rc2?) seems to have fixed the issue - both iPad and Android tablets are now scrolling fine.
Fixed Blocker
| Status | ||||
|---|---|---|---|---|
|
Grace
Appointment date (in the appointment module) appears distorted while using a tablet.
Neither Dennis nor Grace could reproduce; tried other ipads and android tablet.
--
| Status | ||||
|---|---|---|---|---|
|
Vero
Can’t see the translated form labels for the Adult Return visit form when my locale is set to French, for example
There was a module name that wasn't updated
A new e2e test pending to cover this flow in the future - https://github.com/openmrs/openmrs-esm-patient-chart/pull/2266
Fixed Blocker
| Status | ||||
|---|---|---|---|---|
|
by Pius
Dennis
The Error Console is really noisy with this alert whenever I am testing the Global Nav bar: An extension slot with the name 'patient-banner-tags-slot' already exists. Refusing to register the same slot name twice (in "registerExtensionSlot"). The existing one is from module @openmrs/esm-patient-banner-app.
Per Dennis: this happens because the patient-banner-tags-slot extension slot exists in a reusable component. This means that each instance of the slot that gets rendered will have the same slot name. That violates a fundamental principle of the extension system - that slot names should be unique across the app.
Non-issue. it's an intentional warning message because we don't want people to copy what we're doing with the patient banner as if it were a recommended pattern.
Can’t rename things without breaking the patient banner in places.
This is, in fact, the system working as intended in the sense that the extension system isn’t really set up for the same extension slot name to be used by multiple application, so this warning message is generated for the benefit of developers who may not realize they chose a name already in place.
Not blocker
| Status | ||||
|---|---|---|---|---|
|
Grace
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
The question ids of the sub questions in obsgroup questions got incorrectly flagged as duplciate.
https://github.com/openmrs/openmrs-esm-form-builder/pull/409
Not a blocker
| Status | ||||
|---|---|---|---|---|
|
Nethmi
...