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 #13935 Kanban's "BACKLOG" & "ARCHIVE" are missing from User Stories' "Status" field
    Actions
    Infos
    #13935
    Eric (eric.saintetienne)
    2019-10-15 13:56
    2019-09-25 12:17
    15147
    Details
    Kanban's "BACKLOG" & "ARCHIVE" are missing from User Stories' "Status" field

    Steps to re-create the issue:

    • Create a project using the scrum template
    • In the Agile Dashboard: activate Kanban
    • Create a Kanban board for User Stories
    • Go to the User Stories tracker's Fields administration, the Status fields does not contain Kanban's BACKLOG and ARCHIVE status.
      Consequently it's also missing in the Transition Rules (in Workflow for the User Stories tracker).

    Moreover, after you've created a user story, draging and dropping that User Story from the Todo column into the BACKLOG column of the User Stories Kanban board, a popup appears entitled: Oh snap! with the following content:

    An error occured while saving one of your last action.
    We're afraid that you will have to reload the page in order to bring you back to a consistent state.

    Error details

    500 Internal Server Error: The transition to the value "None" is not valid.

                     Cancel                 OK, reload the page

    The problem is that it's just not possible to setup that transition.

    Ideally I'd like to make all new user stories use the BACKLOG status.

    Trackers
    11.4
    EL7 (CentOS|RHEL)
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    New
    Empty
    Attachments
    Artifact links
    Empty
    Empty
    References
    Display settings

    Follow-ups

    User avatar
    Geoffroy Grelot (ggrelot)2019-10-15 13:56
    In the current Kanban UI, "backlog" and "archive" are special columns binded to, respectively, 'None' status value and 'not open' status values (as per the status semantic).
    So, currently, your status field would have not to be mandatory, and your workflow, to allow moving backwards to None. But then, the unspecified status makes the artifact no longer 'open' which prevents it from appearing in Scrum UI's Backlogs; cf. my request #11571 about this discrepancy between both Agile planning UIs.
    User avatar
    Alberto Sampaio de Araujo Neto (alberto.sampaio)2019-10-04 17:26
    Same problem here. Just found this request on Google. The only way to move an artifact to backlog column is disabling trasition rules, which doesn't make any sense in my context.