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

Allow creation of separate swimlanes for stories (and their tasks) and bugs

    • 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.

      When configuring a board, I can choose to "Base Swimlanes" on either Stories or Queries. I'd like to have both types at once: one swimlane for each story (containing their subtasks) and another swimlane for bugs.

      To me, the ideal Scrum board would be like this:

      • Swimlane 1: Story 1 and its tasks
      • Swimlane 2: Story 2 and its tasks
      • Swimlane 3: Bugs
      • Swimlane 4: Technical debt

            [JSWSERVER-6895] Allow creation of separate swimlanes for stories (and their tasks) and bugs

            Vova added a comment -

            That's a valid request also for us. Jira could be so much more useful with this functionality

            Vova added a comment - That's a valid request also for us. Jira could be so much more useful with this functionality
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3064430 ] New: JAC Suggestion Workflow 3 [ 3654559 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]

            Ali added a comment -

            We moved to YouTrack a while back because of this issue. Was just checking in to see if there has been any progress since. Shame Atlassian can't see the value in it.

            Ali added a comment - We moved to YouTrack a while back because of this issue. Was just checking in to see if there has been any progress since. Shame Atlassian can't see the value in it.
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2622580 ] New: JAC Suggestion Workflow [ 3064430 ]

            Here the same, i'm really dream about it. It's frustating that in my board all very important bugs are at the bottom of Kanban -> what makes difference beetwen backlog and sprint view (kanban). I have to make fake Stories and put bugs into this Stories and put in some priority. For me is silly solution ;/

            Please make something with this!!!

            Dominika Rakoczy added a comment - Here the same, i'm really dream about it. It's frustating that in my board all very important bugs are at the bottom of Kanban -> what makes difference beetwen backlog and sprint view (kanban). I have to make fake Stories and put bugs into this Stories and put in some priority. For me is silly solution ;/ Please make something with this!!!
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2317549 ] New: Confluence Workflow - Public Facing v4 [ 2622580 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]

            For me also.  And like @kostantin Stambolov, I would also like to know what alternatives there are for achieving this.  I want to be able to see very clearly the progress on my user stories.  The work on my user stories are done via sub tasks, which are all assigned out to various team members. This works well as, true to the agile principles many members may be working on the same story at the same time.  I would like to be able to see clearly what stage each of the sub tasks for that User Story is at.  Currently everything is just lumped in together.

            @Michael Tokar or any other JIRA Agile Team rep; it would be nice to have some customer support on this, and get an answer to the questions asked over the last 18 months please.

            Deleted Account (Inactive) added a comment - For me also.  And like @kostantin Stambolov, I would also like to know what alternatives there are for achieving this.  I want to be able to see very clearly the progress on my user stories.  The work on my user stories are done via sub tasks, which are all assigned out to various team members. This works well as, true to the agile principles many members may be working on the same story at the same time.  I would like to be able to see clearly what stage each of the sub tasks for that User Story is at.  Currently everything is just lumped in together. @Michael Tokar or any other JIRA Agile Team rep; it would be nice to have some customer support on this, and get an answer to the questions asked over the last 18 months please.

            Why this issue is closed? It would be great. maybe a must have

            Gabriel Fonseca added a comment - Why this issue is closed? It would be great. maybe a must have

            I also think it would be really useful to be able to produce Swimlanes for the residual issues.

            Simon Cordingley added a comment - I also think it would be really useful to be able to produce Swimlanes for the residual issues.
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2038593 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2317549 ]

              Unassigned Unassigned
              4ef46871487e Daniel Serodio
              Votes:
              20 Vote for this issue
              Watchers:
              33 Start watching this issue

                Created:
                Updated:
                Resolved: