closed date set to current data in update orgunit

Bug #646746 reported by Ola Hodne Titlestad on 2010-09-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Lars Helge Øverland

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.

Changed in dhis2:
milestone: none → 2.0.5
importance: Undecided → High
Changed in dhis2:
assignee: nobody → Lars Helge Øverland (larshelge)
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers