← Back to team overview

dhis2-devs team mailing list archive

Re: [Bug 567080] [NEW] dataset-section-no-sorting

 

On 20 April 2010 08:12, jason.p.pickering <jason.p.pickering@xxxxxxxxx> wrote:
> Public bug reported:
>
> When creating a data set section, there is no logical ordering applied
> to the data elements. The first time I created the dataset section, they
> appeared to be ordered alphabetically. When I saved and edited the
> dataset again, the ordering is completely jumbled up.
>

After chatting with Jason I realise my recent tirade was mis-focussed.
 Jason is concerned here about ordering in the dataset section
maintenance module (not the form itself).

Currently we have:

private List<String> selectedList = new ArrayList<String>();
private List<DataElement> dataElements = new ArrayList<DataElement>();

in the various action classes.  I suspect changing List<?> to
SortedSet<?> will provide a quick fix.  Just trying now ...

Bob.


> ** Affects: dhis2
>     Importance: Undecided
>         Status: New
>
> --
> dataset-section-no-sorting
> https://bugs.launchpad.net/bugs/567080
> You received this bug notification because you are a member of DHIS 2
> coordinators, which is the registrant for DHIS.
>
> Status in DHIS 2 - District Health Information Software: New
>
> Bug description:
> When creating a data set section, there is no logical ordering applied to the data elements. The first time I created the dataset section, they appeared to be ordered alphabetically. When I saved and edited the dataset again, the ordering is completely jumbled up.
>
>
>

-- 
dataset-section-no-sorting
https://bugs.launchpad.net/bugs/567080
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:
When creating a data set section, there is no logical ordering applied to the data elements. The first time I created the dataset section, they appeared to be ordered alphabetically. When I saved and edited the dataset again, the ordering is completely jumbled up.





Follow ups

References