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

Jira Software classic boards settings - Swimlanes set by Epics displaying Epics not listed on the board filter.

XMLWordPrintable

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

      Issue Summary

      Jira Software classic boards settings
      If the Swimlanes are set to be based on Epics and there are Stories associated with Epics not returned by your board filter, those Stories won't show up on your Kanban Board / Scrum Active Sprints page.

      Swimlanes based on Epic description:
      Group issues under their epic. Issues not assigned to an epic will be shown in their own group at the bottom. Epics with no issues on the board will not be shown.

      It is expected behavior, however, it can be annoying since Stories with Epics from a different project will vanish from your board.

      Workaround

      Kanban board: Change the board filter to show all existing Epics in Jira plus your project issues.
      For example: issuetype = Epic or project = TEST

      Active Sprints:
      If the Epics and Stories are under different projects but using the same sprint, you can use the workaround above.
      If the Epics and Stories are under different projects and under different sprints, there is no workaround, they won't show up on your active sprints tab at all since active sprints don't show issues that are not part of your sprint.

            [JSWCLOUD-18850] Jira Software classic boards settings - Swimlanes set by Epics displaying Epics not listed on the board filter.

            Matthew Hunter added a comment -
            Atlassian Update - April 2, 2022

            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 prioritize 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 (no votes or comments 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 in https://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!

            Matthew Hunter added a comment - Atlassian Update - April 2, 2022 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 prioritize 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 (no votes or comments 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 in https://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!

              Unassigned Unassigned
              aschneider@atlassian.com Adalberto Schneider
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: