-
Suggestion
-
Resolution: Fixed
-
2
-
3
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
We have project teams that use the Kanban board and would like to be able to selectively display issues by epic. They have a large number of epics (30+). Their preferred solution would be an Epic filter drop-down list, which would also be useful on the Scrum Work view. If that is not possible they would like a Quick Filter drop-down selection instead of the more.../less... that is currently available. With more than 10-12 Quick Filters, the current presentation becomes difficult to use. The drop-down selector could be displayed instead of more... when there are more filters than will fit on one line.
- is related to
-
- Gathering Interest
- relates to
-
- Under Consideration
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-86743] Add Epic filter or drop-down Quick Filter selection on the KanBan board
It is now possible to filter by Epic on a Kanban board:
Does this satisfy the requirements of the watchers of this ticket? Thank you!
Yes, please add this. It's frustrating to our teams that they have to give up this feature to align with other teams by using a company managed project.
Yes we need this. Roadmap has this quick filter by default, but in Kanban board there are no way to set.
many things fit right between the company managed and team managed. this being one of them.
It would be useful to have the drop downs from the team manged project's kanban boards, imported to the team managed project's kanban boards 
Note there's already a ticket for this that's over 8 years old and has over 600 votes in favor of it. I think it's time this moves beyond the "Gathering Interest" phase of development....
Hi Atlassian team,
In the past the drop-down for Quickfilters was implemented for Jira Cloud. I have a screenshot.
Is there any "dark feature" to enable it again?
Link to the screenshot: 
As I did not receive any responses to this comment I am closing this ticket.
If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.