Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #2234 [SOAP] Inconsistent ids for dynamic ugroups
    Actions
    Infos
    #2234
    Stéphane Bégaudeau (begaudeaus)
    2013-02-22 17:55
    2013-01-22 10:43
    1231
    Details
    [SOAP] Inconsistent ids for dynamic ugroups
    Step to reproduce:
    1- create a tracker with a multi select box binded to the groups "project members" and "project admins"
    2- export the XML description or use the SOAP services to retrieve the description of the fields and see that the binding is parameterized with "group members" and group admins" instead.
    3- use the SOAP service "getProjectGroupsAndUsers" to retrieve the groups available and while the groups "project_members" and "project_admins" do exist, the binding information retrieved from the SOAP services or the XML description ("group_members" and "group_admins") do not exist and as such it is not possible to retrieve the members of those binding.

    Tuleap version 5.8.99.17
    API
    5.8
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Mélanie Bats (mbats)
    Stage
    Martin GOYOT (goyotm)
    Closed
    Empty
    Attachments
    Artifact links
    Empty
    By Stéphane Bégaudeau (begaudeaus)
    (31 kB)
    multiselectbox.png
    A screenshot of the binding defined
    By Stéphane Bégaudeau (begaudeaus)
    (11 kB)
    bindingretrieved.png
    A screenshot of the binding received
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Yannis ROSSETTO (rossettoy)2013-02-22 17:55
    Resolved in Tuleap 5.11.99.1
    • Status changed from Verified (disabled) to Closed
    • Platform set to
    • Is an Enhancement or an internal improvement? set to
    User avatar
    Martin GOYOT (goyotm)2013-01-25 10:17
    Hello,

    after further investigations about this bug, I can provide you a temporary bypass before we fix this misbehaviour: you can wrap around group_members and group_admins considering they refer to project_members and project_admins. In fact, if you create a group in your project, and name it group_members or group_admins, when retrieving it with SOAP, it will be called, for instance "ugroup_103", and not group_members as you would probably expect. So it won't break anything.

    Regards,
    User avatar
    Martin GOYOT (goyotm)2013-01-22 16:24
    Hello,

    You're right, I can verify this issue, this is due to an error in the way we manage group names. We'll try to correct it as soon as possible.

    Thanks for your feedback.
    • Status changed from New to Verified (disabled)
    • Assigned to changed from None to Martin GOYOT (goyotm)