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

      We suggest the implementation of an option to hide the "Everything Else" swimlane.

      Context:

      A Kanban board contains "Story" and "Sub-tasks" in its filter and is set to display stories as swimlanes. The stories that contain sub-tasks become swimlanes as expected, however, the ones that don't (or that contain only old hidden completed subtasks) will all show on a swimlane named "Everything else" at the bottom of the board.

      Removing "Story" from the board's filter while keeping "Sub-tasks" will prevent the board from displaying the "Everything else" swimlane, however, the filter won't have the visibility of the parent Epic of the story, and consequently, the Epic labels on the Stories won't be displayed.

      Keeping "Story" on the filter to maintain the Epic labels is necessary in this case, but the the "Everything else" swimlane is undesirable. It can be removed by applying a quick filter on top of the board, however we suggest that a dedicated option to hide the "Everything else" swimlane be implemented on the board's settings, along with the "Expand/Collapse all swimlanes" options.

            [JRACLOUD-91266] Hide "Everything Else" Swimlane on a board

            Atlassian Update - October 31, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Matthew Hunter added a comment - Atlassian Update - October 31, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

              Unassigned Unassigned
              d80b1397fd0f Guilherme Lima
              Votes:
              6 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: