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 #11571 'none' value should be allowed in field semantics/workflow and sparated from Kanban semantic 'backlog'
    Actions
    Infos
    #11571
    Geoffroy Grelot (ggrelot)
    2018-06-26 20:02
    2018-06-04 16:56
    11913
    Details
    'none' value should be allowed in field semantics/workflow and sparated from Kanban semantic 'backlog'
    When 'status' is a non-mandatory field, the value 'none' should be addressed in semantics (e.g. I'd like to define it as 'open' even if blank) and in workflow (e.g. I'd like it to be refined after blank submission, with some conditions about who can do so and comments). 'None' is currently allowed in field dependencies only.
    It's all the more needed as 'none' is currently, AFAIK, the only way to put artifacts in the 'backlog' of a Kanban. So the semantics should also allow to define some selectbox values as 'backlog', the same way as 'open' and 'closed'.
    Trackers
    All
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    New
    Empty
    Attachments
    Artifact links
    Empty
    Empty
    References
    Referencing request #11571

    Artifact Tracker v5

    request #13935 Kanban's "BACKLOG" & "ARCHIVE" are missing from User Stories' "Status" field
    Display settings

    Follow-ups

    User avatar
    Geoffroy Grelot (ggrelot)2018-06-26 20:02
    last edited by: Geoffroy Grelot (ggrelot) 2018-06-26 20:22
    It seems that not being 'open' as per the semantic prevents the artifact from being available in the top backlog of the Scrum planning dashboard.
    Then, currently, a "none"-valued field can't be flagged as an 'open' status in semantics. Thus, it can't be backlogged in Scrum.
    If I'm correct, this would be a major incompatibility between Kanban and Scrum dashboards, since "none" value is currently the only way to put artifacts in the "backlog" column of Kanban.