Created new suggestion ticket (JSWSERVER-21146) in order to request extending this ticket based on the updated requests for quick-filters.

i second Daniel's comment above.  For Atlassian to close a suggestion as if it has been met by the current Epic Search feature, when it clearly hasn't, is disappointing and not very professional.  To be honest, it seems beneath what I expected from you guys. 

I haven't read every single comment so if my comments below have already occurred, please say so.

IMHO, if Atlassian feels that the suggestion breaks or goes against how the app in general and epics specifically are supposed to work, then say that and explain your reasoning.  There will, of course, be those that won't agree, but at least your reasoning for not making any progress on this will be better understood.  Basically, if you have no intention of doing it, then explain why.  If you agree that it does have value but it's low priority, then say that too. 

You guys have been around too long and have matured too much as a company to provide an interface for us to make suggestions and then not provide the active moderation that is expected to go with that.

As much as the epic search is at least something.. It's not really all that helpful..

The trouble (IMHO and which I believe is shared by others), is not a matter of searching the epics pane for any single epic, but of creating a filtered view of the board epics to only a subset of the full board.

We have a number of subteams within our boards, and usually have a couple dozen epics in progress on a board at any one time, but only a fraction of them (5-6) are relevant to any one subteam. We already use quick-filters to create sub-team views of the board, which does work amazingly well for issues but not for the epics pane. (we don't use sub-team boards as the sub-teams are still tightly coupled and highly collaborative, which caused issues when using separate boards)

Hence why I believe the solution many people are looking for is not the ability to search the epics pane, but the ability to apply the quick-filters we already have and use for issues to the epics pane...

Similar expressions are also found in the cloud version: JSWCLOUD-18474

Overall, I would have to say that the current implementation is not truly complete..

(Truthfully, I think the discrepancy is largely because of the vast time since the ticket was originally created..) 

Hi,

I don't want to be a downer, but the new search fields sounds like it will only be a slightly better workaround than my current workaround: Using the search function integrated in the browser (ctrl + f).

..... Coming up on it's 10 year anniversary ... good point @Lee Cash

Dear Jira users,

Jira 8.19 will make working with long epic and version lists a little bit easier. The Versions and Epics sections of the Backlog view will now include new search fields that let you filter as you type. These new elements should facilitate and improve your search experience. We would like to get your feedback on those changes and suggestions for future improvements.

Cheers,

Mateusz Witkowski

Software Engineer, Jira Server and Data Center

+1 

Being able to quickly filter epics while viewing backlog, and then from the reduced epic list select one to see only those issues under that epic, would be a big UX improvement. Ideally it auto-filters as you type, as with the Bitbucket project filter field.

@julien - this is about having quick filters apply to the epic panel.

The board filter seems to apply to the epics too.

If I replace the old filter F, by (F AND type != "Epic") OR (type = "Epic" AND status = "In progress"), it seems to show only the epics in progress. You can then have a separate Kanban that shows the epics to move them around.

The filter can be found in the "board settings".

There are a lot of support requests so I can only imagine the logistical challenge keeping customers informed. That said, this is a critical issue, one of the highest voted requests, and has been in effect for literally years (coming up on its 10 year anniversary). For these reasons alone I would expect Atlassian to at least provide more frequent updates. 

Of course, and unfortunately, I know I'm just shouting into the void at this point. This won't illicit a response from Atlassian. And that's the problem. 

+1

I really appreciate this. If the epics will be sensitive to QuickFilters in the backlog page (left EPIC panel), I will be pleased.