Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-10936

As a Kanban Board user, I would like to group issues by epic link in Swimlanes

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      Hi,

      Our development methodology (based on FDD) uses Kanban and Scrum boards at same time in each project.

      The "Epic" (recognized as "FeatureSet" in FDD) is the main element to group/find/structure all itens in the project scope.

      So, in this way, the analists use Kanban boards (in the overall modeling phase) to discover issues (recognized as "Features" in FDD) and them use the Epics to group them.

      After epics and features pass by "planning" status in the workflow... the programmers visualize them in the proper Scrum boards.

      The problem is that, although the Scrum board (used by programmers) can group issues into the respectively epics (using the Swimlanes config), the Kaban boards (used by analysts) cannot

      I know that we can configure Swimlanes by Queries, but it is improdutive, because (first) we use the same kaban for all projects here and (second) using this approach, we need to configure-and-reconfigure the Kanban board each time that an Epic is created/changed/deleted.

      A nice feature would be Swimlanes by Epics in Kanban board, as show in attached and is currently available in Scrum boards.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              atlassian@3layer.com.br 3layer (expert)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: