dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olatitle@xxxxxxxxx>]

Public bug reported:

Applies to 2.0.5 only - has been fixed in trunk rev. 2087

In UpdateOgranisationForm.vm a function datePickerInRange( 'openingDate', 'closedDate' ) is called.
This function (in common.js) sets to start and end date to current date if they are null or empty.
This is not desired for end date which is not a required (and mostly not desired) field in orgunit update.
Basically this means that any changes to the orgunits cannot be saved as an orgunit with children cannot be closed.

In the fix in trunk rev 2087 the function has two additional boolean parameters which decides whether the current date should be used or not:
function datePickerInRange ( startdate, enddate, setCurrentStartDate, setCurrentEndDate )

There is a lot more in the 2087 commit, and not sure we want all that in
the 2.0.5 branch right now.

** Affects: dhis2
     Importance: High
         Status: New

** Changed in: dhis2
    Milestone: None => 2.0.5

** Changed in: dhis2
   Importance: Undecided => High

-- 
closed date set to current data in update orgunit
https://bugs.launchpad.net/bugs/646746
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.

Status in DHIS 2 - District Health Information Software: New

Bug description:
Applies to 2.0.5 only - has been fixed in trunk rev. 2087

In UpdateOgranisationForm.vm a function datePickerInRange( 'openingDate', 'closedDate' ) is called.
This function (in common.js) sets to start and end date to current date if they are null or empty.
This is not desired for end date which is not a required (and mostly not desired) field in orgunit update.
Basically this means that any changes to the orgunits cannot be saved as an orgunit with children cannot be closed.

In the fix in trunk rev 2087 the function has two additional boolean parameters which decides whether the current date should be used or not:
function datePickerInRange ( startdate, enddate, setCurrentStartDate, setCurrentEndDate )

There is a lot more in the 2087 commit, and not sure we want all that in the 2.0.5 branch right now.