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 #13006 Message "The value 'xxxx' doesn't exist for the list field 'submitted_by'." in Tracker's report
    Actions
    Infos
    #13006
    Jérôme Averty (javerty)
    2019-02-25 11:29
    2019-02-18 16:58
    13878
    Details
    Message "The value 'xxxx' doesn't exist for the list field 'submitted_by'." in Tracker's report

    In Report Tracker,

     

    • In a Report,  on Expert Mode do the request:
      • submitted_by = MYSELF()
    • if a user is not in a field Selectbox 'Bind to users' (example Submitted_by or assigned_to)
    • => The message "The value 'xxxx' doesn't exist for the list field 'submitted_by'." appears

    It's a problem in a request like

    submitted_by = MYSELF() OR assigned_to =MYSELF()

    if the user is not in the liste submitted_by, the result is empty and the message appears

    Trackers
    10.10
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Acknowledged
    Empty
    Attachments
    Artifact links
    Empty
    Empty
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2019-02-25 11:29
    Hi,

    This is in fact the expected behavior.

    The MYSELF() attribute is resolved to yourself and since you are not part of the list the query is rejected.

    That's said I understand why it can be annoying. I'm unsure on what the proper resolution should be. The only way I see to avoid that would be to change the behavior of the verification when MYSELF() is used, e.g. if I'm not in field list named list1 the conditions should be resolved as follow:

    list1 = MYSELF() # False
    list1 != MYSELF() # True


    Doing that would mean we got a different when using MYSELF() or the name of the user as a string directly. I'm not sure having two different behaviors for something that is supposed to do the same thing is the right call as it can be confusing.
    • Status changed from New to Acknowledged