"Help People Upgrade to Platform 2.x" Sprint Announcement

Continuing the discussion from Proposing a sprint to help people upgrade to Platform 2.x (Mozambique tried to upgrade to Platform 2.x, but was blocked for various reasons):

Although OpenMRS Platform 2.0 was released in August of 2016, and our latest release is 2.1.3, many implementations still run on the 1.x release lines. Some of these implemenations would like to upgrade, but haven’t been able to make time to test out the process, ensure that modules are upgraded, etc.

The purpose of this sprint is to help people upgrade, by providing a common time for people to look at this, and by getting community developers to help with the work we identify.

Dates: 7-19 May 2018


  • Implementations running Platform 1.x are ready to upgrade to Platform 2.x
    • eSaude has volunteered
    • we’re still looking for others to try also
  • More modules are upgraded to support Platform 2.x


As a dev, you can work on issues labeled “help-upgrade-platform-2”: https://issues.openmrs.org/issues/?jql=labels%20%3D%20help-upgrade-platform-2

Agile board: https://issues.openmrs.org/secure/RapidBoard.jspa?rapidView=160&view=detail

As an implementation you can work on upgrading, and share any problems you run into.

How to Join

We’ll have a kickoff on Monday 7 May 2018, details TBD.

But you can also just try to upgrade your implementation, and share you experiences on this thread, or just pick up tickets to work on, even if you haven’t attended the kickoff.

Happy sprinting!


@darius thanks alot for the updates.I would like to avail sometime and help out on priority tickets / implementations that would like to upgrade to 2.x

@ssmusoke earlier told me that the METS Team did something to upgrade(Data Entry Statistics Module) UgandaEMR to 2.X , he may want to share something so that may be a starting point for the rest.

@dkayiwa did some work here and here

Thinking about how exactly to approach this sprint, instead of the usual Monday kickoff, I think we can do the following:

If you are trying an upgrade then say so on this thread. (“Hi, I’m testing the upgrade from VERSION to VERSION in an implementation in LOCATION”.) As you run into any issues (or if you’re successful), then report that back here.

If you want to help out then keep a watch here and on IRC to see what problems people are reporting. Also, you can work on the tickets that we already have.

I’m still having some technical difficulties creating the agile board, but you can find the tickets with this JIRA query: https://issues.openmrs.org/issues/?jql=labels%20%3D%20help-upgrade-platform-2

(@dkayiwa if you’re not actively working on RCM-106 then perhaps you can unassign yourself so someone else can pick it up as part of this sprint.)

We can assess based on how things go today whether we need a formal kickoff call in the next couple days.


@darius Thanks alot


We at eSaude Mozambique, are trying to upgrade our implementations which are majorly on OpenMRS version 1.9.2 but we recently upgraded our test environment to 1.11.5. We tried upgrading to 2.x but ran into issues that started this thread. One reason was about the community modules that were outdated and could NOT be compatible. Our upgraded implementation uses docker and one can test our platform here.Thanks @valvijo @emabota @janflowers

1 Like

@ningosi Can you provide a list of the community modules which are outdated

Hi @ssmusoke

I recently documented my findings here Sync2 Testing Report

1 Like

@ningosi see comments on the thread, we are using all the mentioned modules with 2.x u may just need to upgrade to snapshots in some cases, getting them released should not be a show stopper

1 Like

The first error I get when upgrading my 1.11.5 to 2.1.2, anyone else getting that? and we earlier had a discussion about that here Platform upgrade

  1. Can you try to upgrade from 1.11.5 to 2.0.6 first to Ref App 2.7.0 first

  2. Then you can change core to 2.1.2

Can you paste that section of the log at pastebin.com?

here it is https://pastebin.com/HDiizpud

This looked familiar and I found this thread that appeared to be related:

I think there may have been a more recent thread around this, but I can’t find it. @darius @mseaton does this ring any bells?

(We did not run into this issue during our upgrade, fwiw…)

I believe that I created an issue for this already based on Nicholas’s earlier feedback: https://issues.openmrs.org/browse/TRUNK-5383

And here is the thread: Platform upgrade

My personal opinion is that we should solve this in openmrs-core, and not require people to take the manual steps.

Thanks @darius that was the thread I was thinking off and couldn’t find.

I have added a sprint board: https://issues.openmrs.org/secure/RapidBoard.jspa?rapidView=160&view=detail

Please share some updates, as well as also picking up those tickets! https://issues.openmrs.org/browse/RCM-106 is a high priority one.

1 Like

That changeset is in 2.0.5, so I took the manual way of dropping that constraint and I was able to upgrade my 1.11.5 database to 2.0.5. The problem occurred when I tried to restore the constraint back, this is the error

@ningosi the “error” link you gave is a link to stack overflow. Can you please share a link to your actual error?

@ningosi, @valvijo, since we’re a week into this sprint, could you all give an update on how upgrading is going?

@ggomez does any of your team wanna join this sprint?