Skip to main content

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.

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 #10318 Problem with trigger
    Infos
    #10318
    Louis Pauvert (louis.pauvert)
    2017-06-19 09:32
    2017-06-14 15:18
    10569
    Details
    Problem with trigger

    Hello,

    I have 1 tracker for client request and another one for the task linked to the client request.

    I already got some trigger created to do automatic change in the client request when i change a task status its repercuted on the client request.

    I have tested it before it was ok but now i go on my task to change the status from New to Ongoing and when i validate i got error 500 i do f5 and saw that my task status is Ongoing so its ok but my client request didnt go on Dev Ongoing.

    I dont know why it dont work now.

    Trackers
    9.8
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2017-06-19
    Attachments
    By Louis Pauvert (louis.pauvert)
    (39 kB)
    client request after f5.png
    By Louis Pauvert (louis.pauvert)
    (8 kB)
    erreur connexion.png
    By Louis Pauvert (louis.pauvert)
    (21 kB)
    f5 after erreur connexion.png
    By Louis Pauvert (louis.pauvert)
    (43 kB)
    workflow - trigger - client request.png
    References
    Referenced by request #10318

    Artifact

    rel #10117 9.9

    Other

    devel #39228
    gerrit #8711
    Display settings

    Follow-ups

    User avatar
    Yannis ROSSETTO (rossettoy)2017-06-19 09:32
    Integarted into Tuleap 9.8.99.182
    • Status changed from Under review to Closed
    • Connected artifacts
    • Close date set to 2017-06-19
    User avatar
    Thomas Gerbet (tgerbet)2017-06-16 14:59
    I have been able to reproduce the issue but I'm still do not know how it can happen in a "standard" use case. That's said even if a user manipulate directly the inputs he sends that should not crash Tuleap. I'm going to fix it.
    • Status changed from Waiting for information to Under implementation
    User avatar
    Thomas Gerbet (tgerbet)2017-06-16 11:14
    No, it should be sufficient to analyze and potentially reproduce the issue, thank you.
    User avatar
    Louis Pauvert (louis.pauvert)2017-06-15 10:35

    @nterray 

    I got the error from my SysAdmin :

    [Thu Jun 15 10:25:30 2017] [error] [client IP] PHP Catchable fatal error:  Argument 1 passed to Tracker_FormElement_Field_Text::isEmpty() must be an array, string given, called in /usr/share/tuleap/plugins/tracker/include/workflow/Transition/Condition/FieldNotEmpty.class.php on line 141 and defined in /usr/share/tuleap/plugins/tracker/include/Tracker/FormElement/Tracker_FormElement_Field_Text.class.php on line 614, referer: URL

     

    User avatar
    Louis Pauvert (louis.pauvert)2017-06-15 10:07
    last edited by: Louis Pauvert (louis.pauvert) 2017-06-15 10:29

    @nterray I'm asking for it, but i cant understand why it worked before and now it cant

    My trigger seems good, Clis is parent of Clis_task, i worked my transitions so that i can do the change.

    What is exacly needed to make a task change the status on the client resquest?

     

    EDIT : I supprimed all of my trigger in client request and when i pass my task OnGoing, i didnt get the error 500 at the validation but if i get the trigger back i got it again

    User avatar
    Nicolas Terray (nterray)2017-06-14 19:16
    Hi Louis,

    Are there any errors in /var/log/httpd/error_log? And what is the version of your platform?

    Best regards,
    Nicolas Terray
    • Status changed from New to Waiting for information