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 #8988 Artifact created with an incorrect "Empty" status instead of "None"
    Actions
    Infos
    #8988
    Marc TERRIER (mterrier)
    2019-09-11 09:06
    2016-03-24 16:45
    9094
    Details
    Artifact created with an incorrect "Empty" status instead of "None"

    When a user creates a new artifact, the "Status" dropdown list is set on "None" by default, which is not illogical, but once the user validates by clicking on "Submit" or "Submit and stay", the artifact is created with an incorrect "Empty" status, not the "None" status one could expect.

    This may lead to an issue similar to the one reported in community #8966 (artifacts created by mail, with an incorrect "Empty" default status, not appearing in the Backlog column of a kanban).

    Trackers
    8.12
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2019-09-11
    Attachments
    By Marc TERRIER (mterrier)
    (34 kB)
    Status actually empty although combobox was set to None (1).png
    Artifact created with an incorrect "Empty" status instead of "None" (before)
    By Marc TERRIER (mterrier)
    (60 kB)
    Status actually empty although combobox was set to None (2).png
    Artifact created with an incorrect "Empty" status instead of "None" (after)
    References
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2019-09-11 09:06
    While the strange behaviors about the none status has been indeed fixed I think this one is more about the fact that when the user choose "None" in the selectbox it is displayed as "Empty" in the artifact view.

    That's said this request is opened for a while now and nobody else has manifested an interest for it, I'm going to close it. Feel free to re-open or comment if you have an opinion on this.
    • Status changed from Verified to Closed
    • Close date set to 2019-09-11
    User avatar
    Geoffroy Grelot (ggrelot)2019-09-06 18:46
    This one has probably been solved :
    - new artifacts created from GUI without a status submitted are definitely present in reports filtered on "none" status and in Kanban's special 'backlog' column.
    - for artifacts created from CSV import, the discrepancy was recently (11.3) corrected upon request #13458.