Public bug reported:

Version:
    2.0.6-SNAPSHOT
Build revision:
    2343 
Build date:
    2010-10-12 09:22

Description: the conventional order of DE form: customized, section and 
default. This is logical!
Currently, if once a dataset is registered/named/designed with an customized DE 
(by editing inside Maintenance >> Dataset >> Design data entry form), there is 
no-way (with DHIS2 GUI) to remove/delete/disactivate the customized DE form.
So, every-time a user wants to enter data for that dataset... the unwanted 
customized DE form appeared at first... if wanting to switch to section or 
default DE form... he/she has to make unexpected/unwanted clicks every-time the 
dataset chosen.

Unlike data-sections, it's likely to delete a section.

** Affects: dhis2
     Importance: Undecided
         Status: New

-- 
can't remove a customized DE form
https://bugs.launchpad.net/bugs/658961
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:
Version:
    2.0.6-SNAPSHOT
Build revision:
    2343 
Build date:
    2010-10-12 09:22

Description: the conventional order of DE form: customized, section and 
default. This is logical!
Currently, if once a dataset is registered/named/designed with an customized DE 
(by editing inside Maintenance >> Dataset >> Design data entry form), there is 
no-way (with DHIS2 GUI) to remove/delete/disactivate the customized DE form.
So, every-time a user wants to enter data for that dataset... the unwanted 
customized DE form appeared at first... if wanting to switch to section or 
default DE form... he/she has to make unexpected/unwanted clicks every-time the 
dataset chosen.

Unlike data-sections, it's likely to delete a section.



_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Reply via email to