Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

    •  
      request #37184 User group binding ids can be confused with None value
    Infos
    #37184
    Kevin Traini (ktraini)
    2024-03-05 17:41
    2024-03-05 14:37
    38833
    Details
    User group binding ids can be confused with None value

    When you create a list field bind to user groups, a database table store bind ids between the field and user groups. These ids begin from 1, but id 100 have a special meaning (None value). If a bind id use it, when you set None value it will understand another value (a user group).

    This problem doesn't exist for static list because bind ids begin from 101.

    • Old platforms are tricky to fix, because we cannot know if a field set to 100 means None or a user group.
    • New platforms can be fixed by setting initial id to 101 as for static list fields.
    Trackers
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Kevin Traini (ktraini)
    Closed
    2024-03-05
    Attachments
    Empty
    References
    Referenced by request #37184

    Follow-ups

    User avatar
    Joris MASSON (jmasson)2024-03-05 17:41

    The request is closed, but existing Tuleap platforms with tracker_field_list_bind_ugroups_value rows with id = 100 are still affected. There is no way to distinguish between bindvalue_id meant to be "None" value and bindvalue_id meant to match the tracker_field_list_bind_ugroups_value row with id 100. Thus, we cannot fix the data for existing platforms.