-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
33
-
7
-
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
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 ...
+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.
This is a huge issue for us in terms of kanban functionality. Please fix!
Would also appreciate this feature. Very useful after creating a bunch of sprint epics, and then allocating issues to epics.
I agree with the request; at least the epics should be shown on the bottom as Epics without subtasks or issues inside. Similar to how the sprint view in a scrum board works (no subtasks --> at the end of the board "other issues" according to status in each column).
Relevant issue on backlog tab: https://jira.atlassian.com/browse/JSWCLOUD-22100
I agree.
Although Epics should contain other issues. There is a moment of time
between creating the Epic and adding other issues to the Epic. During this
time period Epics are hard to 'see' in the system.
I would prefer to have the option to choose whether or not empty Epics
appear on the Kanban so that there can be a delay between quickly
creating the Epic summary and description before we know what exactly are
the stories that go into satisfying that Epic.
+1