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 #10135 Burndown error when configuration fields are not numerical fields
    Actions
    Infos
    #10135
    Marie Ange Garnier (marieange)
    2017-05-05 15:24
    2017-04-10 16:51
    10414
    Details
    Burndown error when configuration fields are not numerical fields
    Given an artifact with all system fields declared as string
    - remaining_effort
    - duration
    - capacity
    - start_date

    No error should be sent.
    Warning should inform administrators that configuration is incorrect (except for capacity,
    as field is never mandatory)
    Trackers
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Marie Ange Garnier (marieange)
    Closed
    2017-04-19
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #10042 Tuleap Releases 9.7 Delivered 2017-04-27 15:37 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #10135

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/34/8134/15' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 7a96225a46
    User avatar Yannis ROSSETTO (rossettoy) , 2017-04-19 13:08
    request #10135 Burndown error when configuration fields are not numerical fields 1bc2800239
    User avatar Marie Ange Garnier (marieange) , 2017-04-19 12:31
    Referenced by request #10135

    Artifact Tracker v5

    rel #10042 9.7

    Other

    gerrit #8134
    Display settings

    Follow-ups

    User avatar
    Marie Ange Garnier (marieange)2017-04-10 17:09
    • Summary
      -Burndown error when duration or capacity are not numerical fields 
      +Burndown error when configuration fields are not numerical fields 
    User avatar
    Marie Ange Garnier (marieange)2017-04-10 17:08
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes