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 #13642 Int/float value says that field is "Empty" whereas it is 0
    Actions
    Infos
    #13642
    Nicolas Terray (nterray)
    2019-10-02 09:06
    2019-07-18 14:44
    14823
    Details
    Int/float value says that field is "Empty" whereas it is 0

    My remaining effort has been set to 0 (all tasks done). When I edit the field it says 0, but in read only mode it says "Empty" which is wrong because there is a value:

    1802-empty-value-for-0.gif

    Empty
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2019-08-25
    Attachments
    By Nicolas Terray (nterray)
    (46 kB)
    empty-value-for-0.gif
    References
    Referencing request #13642

    Git commit

    tuleap/tuleap/stable

    Numeric (float or integer) value says that field is "Empty" whereas it is 0 a2c545812e
    User avatar Yannis ROSSETTO (rossettoy) , 2019-08-24 15:19
    Referenced by request #13642

    Artifact Tracker v5

    rel #13668 11.6

    Other

    gerrit #15931
    Display settings

    Follow-ups

    User avatar
    Nicolas Terray (nterray)2019-08-25 10:20
    gerrit #15931 integrated into Tuleap 11.5.99.29

    You're right it was not a computed field.

    Thanks for the fix.
    • Summary
      -Computed value says that field is "Empty" whereas it is 0 
      +Int/float value says that field is "Empty" whereas it is 0 
    • Status changed from Under review to Closed
    • Connected artifacts
    • Close date set to 2019-08-25
    User avatar
    Yannis ROSSETTO (rossettoy)2019-08-24 14:38
    Hello,

    In your gif it seems that it's not a computed field (because there is no "back to autocompute" button).
    Can you confirm that your field is a integer/float field ?
    • 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