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 #8121 Using masschange on Task based artifacts resets assignments
    Actions
    Infos
    #8121
    Mike Lecours (mlecours)
    2015-10-08 10:22
    2015-06-04 18:18
    8144
    Details
    Using masschange on Task based artifacts resets assignments
    Using mass change on a group of tasks to change another field reset all the assignments fields to the group to "blank".
    Steps to recreate:
    1. Select a group of tasks in the report screen with a filter
    2. Use masschange to change a common field (for example, due date)
    3. Note that the assignment fields for each of the artifacts changed has be reset to "blank" (assignments deleted).
    Trackers
    All
    CentOS 5 + php53
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Sandra Echinard (sechinard)
    Closed
    2015-10-08
    Attachments
    Artifact links
    Empty
    By Mike Lecours (mlecours)
    (19 kB)
    Tracker_BMTSK.xml
    tracker xml
    References
    Referencing request #8121

    Release

    release #112
    Referenced by request #8121

    Artifact

    art #8243
    Display settings

    Follow-ups

    User avatar
    Sandra Echinard (sechinard)2015-10-08 10:22
    Fix integrated in Tuleap 8.6.99.58.
    • Category set to Trackers
    • Status changed from Under review to Closed
    • Assigned to changed from None to Sandra Echinard (sechinard)
    • Reported in version set to All
    • Close date set to 2015-10-08
    User avatar
    Timothee TRONCY (timteam)2015-09-08 11:56
    last edited by: Timothee TRONCY (timteam) 2015-09-08 13:57
    Danger !!!

    Please, Increase severity of this artifact. It Is really a critical issue. I have a numerous use of this functionality in Tuleap that reinitialized All select box fields of trackers.

    It looks like a Priority N°1!!!!
    User avatar
    Manuel Vacelet (vaceletm)2015-07-27 16:13
    This is a scary issue, probably here since a long time...
    • Status changed from Verified to Under implementation
    User avatar
    Manuel Vacelet (vaceletm)2015-07-27 15:38
    I managed to reproduced the issue with the XML you attached.

    As identified in art #8243, this bug only affect multiselect box fields.
    • Status changed from New to Verified
    User avatar
    Manuel Vacelet (vaceletm)2015-07-15 10:41
    Could you attach the XML structure of your tracker so we can try it, there is maybe sth that conflicts.
    User avatar
    Mike Lecours (mlecours)2015-07-10 20:29
    So I just tried it on version 8.3.99.29 with CentOS release 6.6 and it still does the same. Even though assigned to says unchanged, all the assignments are set back to "none"
    User avatar
    Mike Lecours (mlecours)2015-07-09 17:12
    I'm in the process of doing that now. Do you have any links to good migration strategies? I'm forced to change servers and can upgrade in place.
    User avatar
    Manuel Vacelet (vaceletm)2015-07-09 17:09
    Did you try with a more recent version (8.3 or 8.3.99.X) ?
    We've made an heavy usage of this feature lately on one of our platforms and we didn't had such an issue.
    I even tried it on my local dev server (8.3.99.27 ATM) and everything works as expected (I changed severity on 3 artifacts)