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

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

Alex Fosdick does bring up a good point. Does atlassian actually reviews these requested features and provides consistent feedback/timing to customers ? I think this website is used to keep customers waiting for ever while Atlassian continue to release carp features that nobody wants to use. My point is, this process of voting for a feature is broken. I am personally frustrated with the Atlassian tools especially Jira. If Atlassian does not listen to its customers, I will just switch to an alternative company that values my opinion and actually listen to me. 

To follow up from @sebastien This is one of the top three requests by votes for features on JW Data Server Jira Project. What is the point of voting for issues, if the top three voted issues seem to have been sitting for years.

People keep requestiing this feature (184 comments so far), yet the last update we had was that it is "considered for development" as of February 2018.

Any chance that this gets bumped in priority or to have an update on when we can expect to have some filtering capacity on Epics?

Thanks.

+1

+1

+1

+1

+1

+1

+1

+1 This list is almost un manageable. We also cannot filter these epics based on what we're currently working on. I don't need to see epics that are still in a phase where my team has no action items. 

Our tool will let you filter the panel using JQL or predefined filters

https://marketplace.atlassian.com/apps/1215334/agile-tools-filters-for-jira-software?hosting=datacenter&tab=overview

+1

+1

+1

+1 !!

+1

+1

+1

8 years.  How is this still under "future consideration?"

At least being able to apply version filter to Epics....

This feature is fundamental in navigation and filtering of a large backlog, i.e. only see Epics related to one specific Component (=sub-project).

I have quite extensive experience with Visual Studio/TFS (+7 years, 10's of projects) and have never lacked any functionality like this. I don't have too much experience with Jira, but so fare I have recognised this as one of the major bottlenecks for me and my projects in managing the backlog efficiently.

So, unless I have missed something essential in how to use Jira, I would strongly recommend Atlassian to prioritise this feature!

Yes, please apply Quick Filters to Epics too.

The similar request from our user, they want to hide the irrelevant epics on the panel.

+1.

+1

+1. This feature would be an incredible improvement to my team's workflow - please consider picking it up in the near future.

Hung, could you not do a new board, and then the board master-filter only shows those? I know that's a nasty hack, but I see your point here in the backlog screen. 

@Mat Chavez, you may have missed the point here. We use that group of "related" epics into so-called Initiative too. But in the Backlog board, the Epic panel only display a flat list of all epics, regardless of group (Initiatives). Here is where the request comes in: we need some way to filter of the list to stay focus on those we are interested in at this time.

For whatever it's worth to people arriving at this, we've hacked a stupid way of joining Epics, and it may help?

• Create a new issue type, like "Roadmap Item" or whatever fits your team
• Associate Epics as "related" or some other relationship, maybe even a custom "contained/container of epics" relationship.
• Create a board that handles just "Roadmap Items"
• Set a separate workflow with appropriate states for "Roadmap Items" as needed.

Not ideal, but it helps. Good luck.

Hey Atlassian; its been about 18 months since you updated the review status of this issue.

Can you please reconsider this? Its being a big bother for us in our workflows and we're struggling to find workarounds other than cluttering everything with unnecessary projects to break things down. We'd rather not have to do that.

+1

+1

+1

+1

+1

+1

Even the ability to hid epics with 0 issues would be useful.

+1
Would like this on Cloud as well, as we're using a board across multiple projects to manage a single team assigned these projects. The fact that Quick Filters do not hide Epics that do not apply is a bit counterintuitive and makes the backlog interface basically unusable.

Its been a year now since last Atlassian update on this issue. Please please fix this!

+1

The huge amount of epics leads to unmanagable backlog view, especially if the board is cross-project

+1, we have over 200 epics and it is a pain to scroll through.  It basically negates the use of drag/drop and we end up having to go into the issue and change the Epic Link field manually, as then we can type in the name to get the right one.

+1

+1

I d like to see this too. In the backlog view the list of epics quickly gets quite long, and it s not handy to scroll up and down or identify my epics or ...

This would be an extremely beneficial feature. It is really hard to see progress on a specific epic within an iteration. In this case, we have a time-sensitive epic that we are looking to complete and I am unable to easily see our progress toward that goal across the team. 

very important feature missing here, when you have to filter (for example non urgent) epics quickly...

workarounds, like creating multiple filters, are multiple pitas