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 #9429 Warnings about unsupported fields in the error log view
    Actions
    Infos
    #9429
    Patrick-Jeffrey Pollo Guilbert (epatpol)
    2016-08-30 17:40
    2016-08-29 23:05
    9706
    Details
    Warnings about unsupported fields in the error log view
    When fetching an artifact, there seems to be some warnings about unsupported fields. Maybe the Tuleap API changed since then. Or maybe the API didn't change but new fields appeared in the Tuleap tracker format, so these warnings appear with later versions.

    I don't know if we need to do something with these new fields, or simply ignore them for now.
    Mylyn
    8.18
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2016-08-30
    Attachments
    Empty
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Patrick-Jeffrey Pollo Guilbert (epatpol)2016-08-30 17:37
    I'll remove those warnings as I think they clutter the error log too much and they're not really useful for the connector views anyway.

    Thanks Manuel
    User avatar
    Manuel Vacelet (vaceletm)2016-08-30 17:02

    The third one is the ability to set context static text (like a description of something you are waiting for in a text area). I would ignore it as well because if not properly placed the text might have no sense at all.

    User avatar
    Patrick-Jeffrey Pollo Guilbert (epatpol)2016-08-30 16:57
    Yea that's what I thought too.

    So far the types of tracker fields giving warnings are : fieldset, column and staticrichtext. I can ignore the first two for now but what is the third one?
    User avatar
    Manuel Vacelet (vaceletm)2016-08-30 09:15

    There are 2 types of fields:

    • The structural/separators fields (columns, fieldset, etc) that were originally ignored because the format of Mylyn task GUI cannot be adapted easily to match what is designed in Tuleap Trackers
    • New fields that were introduced in the meantime (between original development and now).

    For the first, I don't think it's really relevant to anything different. For the second one, we might start by identifying the "new" fields and decide what to do with them.