Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10936

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • AgileBoard
    • JIRA 6.2.5
      JIRA Agile 6.4.2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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.

        1. kanbanByEpics.png
          kanbanByEpics.png
          55 kB

            [JSWSERVER-10936] As a Kanban Board user, I would like to group issues by epic link in Swimlanes

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3069303 ] New: JAC Suggestion Workflow 3 [ 3662526 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626362 ] New: JAC Suggestion Workflow [ 3069303 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2323838 ] New: Confluence Workflow - Public Facing v4 [ 2626362 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2041891 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2323838 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2029919 ] New: JIRA PM Feature Request Workflow v2 [ 2041891 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 735714 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2029919 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Business Value Original: Expected [ 10501 ]
            Workflow Original: GreenHopper Kanban Workflow v2 [ 701709 ] New: JIRA PM Feature Request Workflow v2 [ 735714 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Martin (Inactive) made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Martin (Inactive) made changes -
            Link New: This issue duplicates GHS-9144 [ GHS-9144 ]

              Unassigned Unassigned
              d943dc964ec6 3layer (expert)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: