In the 2.25 User Interface, once a closed date has been set for an
organisation unit, it cannot be removed. Since the closed date field is
optional, there should be some way to remove it, if it has been set
accidentally.
** Affects: dhis2
Importance: Undecided
Status: New
Bug description:
In the 2.25 User Interface, once a closed date has been set for an
organisation unit, it cannot be removed. Since the closed date field
is optional, there should be some way to remove it, if it has been set
accidentally.
When an organisation unit has a closed date assigned, the UI displays an
"X" for removing the date. The X is displayed all the way to the right
on the "closed date" field, so it may be hard to spot if you're on a
wide screen.
However, if you try to submit the form when the closed date is removed
you'll get a "500 Internal Server Error" because the "closedDate" field
will now be set to "", which is not a valid date.
Bug description:
In the 2.25 User Interface, once a closed date has been set for an
organisation unit, it cannot be removed. Since the closed date field
is optional, there should be some way to remove it, if it has been set
accidentally.
Bug description:
In the 2.25 User Interface, once a closed date has been set for an
organisation unit, it cannot be removed. Since the closed date field
is optional, there should be some way to remove it, if it has been set
accidentally.
Bug description:
In the 2.25 User Interface, once a closed date has been set for an
organisation unit, it cannot be removed. Since the closed date field
is optional, there should be some way to remove it, if it has been set
accidentally.
Bug description:
In the 2.25 User Interface, once a closed date has been set for an
organisation unit, it cannot be removed. Since the closed date field
is optional, there should be some way to remove it, if it has been set
accidentally.