OpenMRS Atlas GSoC 2019 — Week 5
1 min readJun 30, 2019
Week 5 has come to an end and we’re getting closer to the deployment of Atlas 3.x to production. This week consisted of mostly bug fixes, and a lot of tickets were solved. Burke was extremely responsive this week and PRs got merged daily, really speeding up the process. Atlas 3.x was merged into master by Cintia yesterday. I also got contributor rights on the repo, so that’s nice. :)
Since the Rest API for types/versions/distributions got merged (ATLAS-145), testing the admin pages became possible. Testing revealed a lot of bugs that were fixed immediately (ATLAS-152, ATLAS-153), but the types interface which got merged by then required another ticket (ATLAS-156).
Some other notable issues were:
- ATLAS-154 — Show patient/encounter/observation counts only if the creator chooses to do so.
- ATLAS-158 — Version’s dropdown when creating/editing a marker is empty.
- ATLAS-160 — OpenMRS version of a marker wasn’t getting saved.
- ATLAS-161 — Viewing markers by distributions was marking all markers as ‘Other’.
- ATLAS-163 — Start fading a marker only after a year has passed.
- ATLAS-164 — Create an ‘update’ button to update a marker and say that its alive.
- ATLAS-165 — Saving a marker doesn’t update the ‘Last Updated’ updated date until the page is reloaded.
- ATLAS-172 — Some markers had saving issues due to response header mismatch.
- ATLAS-179 — Updated a few node packages that had security vulnerabilities.
