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 #8966 Issue with the value set for the status field when created via email
    Actions
    Infos
    #8966
    Patricia Carrasco (pcar)
    2018-02-09 16:07
    2016-03-17 21:24
    9073
    Details
    Issue with the value set for the status field when created via email

    <p>We would like to create an artifact via email.&nbsp; We use this tracker on a Kanban board.&nbsp; What we have noticed is that artifacts created by email are not displayed in the Backlog column.&nbsp; This has to do with value of the status field when sent via mail (when you open the artifact the field is &quot;empty&quot;)</p> <p>We have done some tests and what we have noticed is that if an artifact is created via the REST API with just the Title (since no other field is mandatory), the artifacts appears correctly in the Backlog column on the Kanban board (the status field is &quot;empty&quot;).&nbsp; When an artifact is created via email, it does not.</p>

    Trackers
    8.11
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Emilio Palmiero (empa)
    Stage
    Empty
    Closed
    2018-02-09
    Attachments
    Empty
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Patricia Carrasco (pcar)2018-02-09 15:59
    I just tested creating an artifact by mail. The newly created artifact is appearing in the Backlog column. So the request can be closed.
    User avatar
    Patricia Carrasco (pcar)2016-04-25 17:48
    Same issue also occurs for imported artifacts. They do not appear in the Backlog column of a Kanban.
    User avatar
    Marc TERRIER (mterrier)2016-03-23 17:33

    I confirm that artifacts created by mail have some of their properties, especially the status, that are left uninitialized or initialized to an incorrect value, and that it prevents those artifacts from appearing in the backlog column of a kanban. This is because to appear in the backlog column, an artifact must have its status set to None, but here, the status isn't set to anything, not even to None. There are two ways to verify this:

    1. If you take an artifact created by mail and manually change its status to None, it automagically appears in the Backlog column.
    2. If you use the API Explorer to check the properties of an artifact created by mail, only properly set properties are returned, and Status doesn't appear in the results. If you do the same for an artifact created by mail, after manually setting its Status to None, it appears in the results returned by the API Explorer.
    • Status changed from New to Verified