We can set the timing for this as needed to maximize who can participate, and it would be great if a team that actively would like to upgrade to Platform 2.x is participating! (Can you give more clarity about what “after the beginning of May” actually means?)
Any other groups and individuals interested in participating?
I would suggest that if you generally want to upgrade to the latest OpenMRS Platform releases, you would do well to schedule trying to do this simultaneously with others on this sprint, so that we can identify, analyze, and fix any upgrade issues quickly with everyone focused on it.
I am starting to create/collect tickets for this sprint (and I created a label in JIRA: help-upgrade-platform-2):
- TRUNK-5383 - Automatically handle upgrading data model to 2.0 even when the reporting module is installed
- RCM-106 - Patient searches return 0 results on platform 2.1
- TRUNK-5384 - Use new Implementation ID server URL, and support redirects and https in our custom HttpClient class
@ningosi there are some things I want to confirm with you:
- You mention a “patientflag rest” module. I don’t know what this is. Can you point to the code or omod?
- You mentioned a form filter module. Is that this one? GitHub - openmrs/openmrs-module-formfilter: OpenMRS module that helps in filtering forms on form entry tab of patient dashboard.?
Still to do:
- Check why the following modules that supposedly should work on 2.x didn’t work for @ningosi:
- ensure patientflags supports 2.x, and create ticket if not
- create ticket for updating GitHub - openmrs/openmrs-module-formfilter: OpenMRS module that helps in filtering forms on form entry tab of patient dashboard. to support platform 2.x