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

Show Epics with No Stories on Kanban Board When Swimlanes are Based on Epics

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 34
    • 7
    • 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.

      I have my agile board set to swimlane based on epics, which my teams love. However I've noticed that epics without stories don't show at all, making it easy to lose track of things if you're attempting to build out an epic from the board. It would be nice to add a toggle onto the "Swimlane" screen to turn off this functionality so that empty epics still show as swimlanes, just with no tickets in them.

            [JSWCLOUD-15533] Show Epics with No Stories on Kanban Board When Swimlanes are Based on Epics

            +1

            Cloudapper added a comment - +1

            It is amazing how many problems I find in Jira were reported years ago, but they are still not solved.

            And Atlassian support is asking, why we are considering leaving Atlassian products ... 

            Josef Širůčka added a comment - It is amazing how many problems I find in Jira were reported years ago, but they are still not solved. And Atlassian support is asking, why we are considering leaving Atlassian products ... 

            +100

            Ricky Stillwell added a comment - +100

            jonathan added a comment -

            +1 This would be very useful

            jonathan added a comment - +1 This would be very useful

            +1

            Alexey Sokolov added a comment - +1

            +1

            Teryl La added a comment -

            +1 

             

            Teryl La added a comment - +1   

            +1

            Bob Noseworthy added a comment - +1

            +1

            vincent.king added a comment - +1

            Rommel Villa added a comment - - edited

            +1

            • This affects usability and Jira adoption for non-technical users. If we had an on-going epic reserved operations and maintenance (bugs, requests, adminsitration), already I have had users that find the board intuitive, but will not be able fathom how to find empty epics to add their issue (which is later triaged and verified by the team).
            • I am trying to champion Jira for the organization, and have all employees empowered to use the tool. This is a blocker that makes it hard to promote the tool within the org for a less technical audience and just want to monitor and enter their issues on the boards. I want to streamline the process where users should not need to go to a developer or PM to enter issues for them, as the PM would prioritize and triage the issues in the backlog, and select what's for development.

            Rommel Villa added a comment - - edited +1 This affects usability and Jira adoption for non-technical users. If we had an on-going epic reserved operations and maintenance (bugs, requests, adminsitration), already I have had users that find the board intuitive, but will not be able fathom how to find empty epics to add their issue (which is later triaged and verified by the team). I am trying to champion Jira for the organization, and have all employees empowered to use the tool. This is a blocker that makes it hard to promote the tool within the org for a less technical audience and just want to monitor and enter their issues on the boards. I want to streamline the process where users should not need to go to a developer or PM to enter issues for them, as the PM would prioritize and triage the issues in the backlog, and select what's for development.

              Unassigned Unassigned
              a9373970cdd2 Haddon Fisher
              Votes:
              114 Vote for this issue
              Watchers:
              72 Start watching this issue

                Created:
                Updated: