← Back to team overview

dhis2-devs team mailing list archive

[Bug 719805] Re: More than one compulsory orguntit group set member can be chosen

 

Good point. Definitely a bug. All group sets are now by definition
exclusive, meaning that only one group from a group set can be selected.

This means we can change from a multiple select area to a dropdown, and that
we can include all the compulsory group sets in the same page to speed up
this process.

On Wed, Feb 16, 2011 at 7:05 AM, jason.p.pickering <
719805@xxxxxxxxxxxxxxxxxx> wrote:

> ** Summary changed:
>
> - More than one compulsory orguntit group set can be chosen
> + More than one compulsory orguntit group set member can be chosen
>
> --
> You received this bug notification because you are a member of DHIS 2
> coordinators, which is the registrant for DHIS.
> https://bugs.launchpad.net/bugs/719805
>
> Title:
>  More than one compulsory orguntit group set member can be chosen
>
> Status in DHIS 2 - District Health Information Software:
>  New
>
> Bug description:
>  This may or may not be a bug, but when creating orgunits, it is possible
> to select more than one compulsory organization unit group per group set.
> This is in itself OK I guess, if the groupset is not exclusive (which seems
> not to be possible to set).
>  At any rate, it results in a data integrity violation.
>
>  It this a bug or a blueprint?
>
>
>


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

** Changed in: dhis2
     Assignee: (unassigned) => Thu Tran (tran-hispvietnam)

** Changed in: dhis2
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/719805

Title:
  More than one compulsory orguntit group set member can be chosen

Status in DHIS 2 - District Health Information Software:
  Confirmed

Bug description:
  This may or may not be a bug, but when creating orgunits, it is possible to select more than one compulsory organization unit group per group set. This is in itself OK I guess, if the groupset is not exclusive (which seems not to be possible to set). 
  At any rate, it results in a data integrity violation. 

  It this a bug or a blueprint?



References