DHIS2 patch release 2.33.5 is now available

Dear all,

DHIS2 version 2.33.5 (patch release) is out with bug fixes, security patches and enhancements.

This is the latest stable release for version 2.33, and supersedes releases 2.33.0 to 2.33.4.

The release note for this patch can be found here: Patch 2.33.5 Release Note.



Release Information Links
Release Note Patch 2.33.5 Release Note
Upgrade notes 2.33 Upgrade notes
Download release and sample database https://www.dhis2.org/downloads
Documentation and Javadocs https://docs.dhis2.org/2.33/en
Source code on Github https://github.com/dhis2/dhis2-core/releases/tag/2.33.5
Demo instance https://play.dhis2.org/2.33.5/
Docker docker pull dhis2/core:2.33.5
for more docker image variants see dockerhub
1 Like

Thank you @phil and all developer staff for your work during the months of vacation and pandemic block.
I see and test on the Demo server that one of the bugs we reported and which blocked our error-correction work is resolved - 1. DHIS2-8730 - Capture Web App - Event list Filter - type mismatch.
Thank you so much for this!

I know I’m a nuisance, but I wanted to ask when the resolution of the other bug reported by me could come into your schedules - DHIS2-8729
"Option Group Set - No dimension created"
It would allow us to generate more flexible statistics for different grouping of the ICD-10 diagnosis, which is very important in this period. See my previous posts for more detailed explanation.

The feature of the dimension creation for the Option Group Sets is defined in the documentation of the v.2.31. Now we have the DHIS 2 v.2.34 and the feature is still not functioning.

Thanks in advance!


Any reason this bug fix didn’t make it to this patch?

Hi @antonia,

I’ll bring 8729 to the attention of the Product Managers, but I cannot make any promises regarding how it will be prioritised.

Kind regards,

Hi @Edward_Robinson,

At first glance it seems this issue was fixed by someone outside the core team, and only fixed in our development branch; the full process for bug-fixing and porting to versions under maintenance has not been followed.
I’ll bring this to the attention of the Product Managers so that they can move it into the correct state and follow up (as of now it is not even prioritised for fixing, which is why the inconsistent state has not come to our attention before).

Kind regards,

1 Like

Thanks so much @phil!

Dear @phil, @geetha, and developers,
Unfortunately the issue is not resolved in the v.2.33.5 (the solution is working only for some particular cases but not for the generic case, including our problem), see my today comment in

Kind Regards,

Hi @antonia,

Thanks for bringing this to our attention, I flagged this to the respective developer. :slight_smile:


Hi @Gintare,
thanks for reopening the issue. I just add some additional info for the tests made, in order to help the developers and testers.

Kind Regards,