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 #9307 Computed fields have to take into account numeric values from selectboxes
    Actions
    Infos
    #9307
    Yannis ROSSETTO (rossettoy)
    2016-07-18 15:22
    2016-07-05 08:50
    9589
    Details
    Computed fields have to take into account numeric values from selectboxes
    Since Tuleap 6.11.99.23, Tuleap's computed fields are no more able to take into account numeric values from that come from a selectbox field.
    Trackers
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Reza Charghi (rezachar), Emilio Palmiero (empa)
    Stage
    Empty
    Closed
    2016-07-05
    Attachments
    Artifact links
    Empty
    By Patricia Carrasco (pcar)
    (18 kB)
    Tracker_sprint.xml
    tracker xml
    By Patricia Carrasco (pcar)
    (26 kB)
    tuleap8.15.PNG
    Tuleap 8.15
    By Patricia Carrasco (pcar)
    (32 kB)
    tuleap8.16-5.PNG
    Tuleap 8.16-5
    References
    Referencing request #9307

    Artifact Tracker v5

    rel #9210 8.17

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/28/6128/5' of ssh://gerrit.tuleap.net:29418/tuleap into stable cbb3540e9c
    User avatar Nicolas Terray (nterray) , 2016-07-05 11:42
    request #9307 Computed fields have to take into account numeric values from selectboxes a70f6da621
    User avatar Yannis ROSSETTO (rossettoy) , 2016-07-05 11:30
    Merge branch 'stable' into HEAD 9bb6ef4152
    User avatar Nicolas Terray (nterray) , 2016-07-08 10:50
    Referenced by request #9307

    Other

    gerrit #6128
    Display settings

    Follow-ups

    User avatar
    Marie Ange Garnier (marieange)2016-07-18 15:22
    We are not able to backport the bug in tuleap enterprise, if we backport it we will break something else in computed fields V2.

    You will have to wait until Thursday to have the fix.

    Best regards.
    User avatar
    Patricia Carrasco (pcar)2016-07-18 13:46
    Hi, will this fix be available in an enterprise build later today. We are upgrading our production server on July 23 and we would need this fix. Thanks
    User avatar
    Marie Ange Garnier (marieange)2016-07-18 09:53
    Hello Patricia,

    When I examine your xml, in your tracker you got two computed fields :
    - total effort which target is effort_estimate
    - remaining effort which target is effort_remaining
    so you didn't loose tour target field.

    I cannot reproduce your issue on my side. Can you give me the version used for your tests ?

    Best regards.
    User avatar
    Yannis ROSSETTO (rossettoy)2016-07-15 17:50

    Hello Patricia.

    "Now when you create a Compute Value field you no longer have an option to enter the Target field"

    • Exactly, the new computed fields take into account field from linked artifacts that have the same shortname (same behaviour as old option named fast compute)

    "if you have existing projects that have used Compute value fields and there is data in those field, now it shows as empty".

    • This point is not correct. There must be no changes for computed field v1. Is it possible to share with us the computed field options for this field in particular ?

     

    User avatar
    Patricia Carrasco (pcar)2016-07-15 17:42
    Hi, we have installed a build which contains this feature. Now when you create a Compute Value field you no longer have an option to enter the Target field. Also, if you have existing projects that have used Compute value fields and there is data in those field, now it shows as empty. Is there a bug related to this feature or is there something that I did not understand. Thanks
    • CC list set to Emilio Palmiero (empa), Reza Charghi (rezachar)
    User avatar
    Nicolas Terray (nterray)2016-07-05 11:45
    Integrated into Tuleap 8.16.99.36
    • Status changed from Under review to Closed
    • Close date set to 2016-07-05