Org unit closed date not enforced for event data entry

Support - Assistance technique
1

Hello everyone,

I have an org unit (__PS Saourou, level 6) with a closed date set to 30 September 2025. However, in the Capture app I was able to register and complete an event dated 13 June 2026 — well after the closed date — without any validation error or warning.

For aggregate data entry, the opening/closed dates are enforced and block periods outside the active window. But for event/tracker programs, it seems the closed date is simply ignored for the event date.

My questions:

  1. Is this the expected/intended behavior ?
  2. If so, what is the recommended way to prevent event registration after a given date for a specific org unit?
  3. Is there any plan/Jira issue to align this behavior with aggregate data entry?

I’m on DHIS 2.41.

Evidences :

image
image1265×179 4.02 KB

image
image1094×792 59.7 KB

Best Regards

2

Hi @didate

Thank you for raising this issue. It appears to be a known bug issue: Opening and closing date not being taken into account in Capture app - DHIS2-17544. I will raise this again to the team. :folded_hands:

3

Hello @Gassim ,

Thank you for raising it again in jira. Hope it is going to be fixed soon.

Have a good one.