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. 

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

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

I have teams that have many epics that their teams are working on.  Having the ability to filter them would be absolutely crucial to the work for our roadmaps.  We have custom boards that are filtered by component, so the component trick wont work for this team.

+ 1 Filtering epics would be great. Also if we click on epic the right hand details widget can show epic details. It is a context switch everytime we need to open a different tab to see the details of the epic from backlog view.

+1

+1 - really needed this capability. List of active epics can get really long. If we can filter using some sort of pattern matching, that would be really helpful

+1 - I cannot believe this was logged in 2012 already and to date, has not been addressed at all... I might really be over simplifying this, but if you filter your issues, why can't the epic panel just show available epics for the filtered issues? There can always be a "revert to default filter" or "show all epics"?

Regarding the user filtering, at least I created a board for each team member which is just visible to them and as soon as they move their issues on their board, it is reflected accurately on the main board.

Having the ability to filter epics on other fields on the main board will still be helpful to the managers viewing the full board.

@Leslie: Done Epics do not appear in the epic panel, but you have to set the field epic status to done, not just the "normal" status.

BR

I do not need (nor want), to see epics that are Done in my epic view. A filter would be really useful.

Filtering and searching of the epics in the backlog is really necessary!

We really need this trying to figure out a way to do this now.

Thanks.  Note that this issue (JSWSERVER-6949) is against Jira Server, not Cloud, so that's why your approach isn't a workaround or solution to what we're describing.  Perhaps we can hope that this functionality in Jira Cloud will come to Jira Server in a future version.

Thank you @Wenqin for validating and supporting my approach. Having different boards for each component and one "master" board also can come handy for Sprint Planning in a multi-team context: PO and teams work on the master board during SP1 and on (multi-)team-only boards in SP2 and later. Of course, exchanging technical components with customer concerns leads to product thinking and aligns better to markets.

Hi John, I can't find my Jira version. It is probably the latest cloud version. What I was describing is the same as Michael's approach. It involves creating separate boards for component(s). But I don't think you lose much convenience by creating separate boards, as you can have one master board that includes all components, and other child boards with specific components. You can toggle them with a dropdown that is auto-generated by Jira on the toolbar. The amount of clicks to navigate between boards are basically the same as switch on the off filters within one board.

@Wengqin Chen, what version are you using?  I'm not seeing the pattern you are describing in Jira Software 7.5, and I'd love for us to be able to use what you describe.  Michael appears to be describing creating a separate board for each component, which will indeed reduce the number of epics shown, but at the cost have having to deal with separate boards.  Your pattern appears different.

@Michael is right. I tried his way and it worked! There is no need to install any plugin in order to filter epics by component in backlog. Here are the steps: Go to Backlog -> click on "..." icon on the very top right corner -> click on board settings -> under "Saved filter", click on hyperlink "Edit Filter Query". -> it takes you to a new page, in the filter section on the top, click on "More" dropdown, in the dropdown select "Component", a "component" option appears and set it to your desired component -> click "Save" that now appears on top of the page -> now go back to your backlog, without clicking on any filters, you should see both the epics and the issue already only displaying those in the desired component. 

This took me way too long to figure out, so I want to share with the community. Hopefully this will help someone in the future!

Help with Agile Board Filter Plugin

Can I filter Sprints to show in the backlog view ?

I have one Jira Project to my product and many development projects in my product. Each dev project is a "version".

So, with Agile Board Filter Plugin I can only one Board to all my dev projects just by choosing the "version".

My problem is to filter the Sprint because I have many teams in many differents projects ("versions") and each on with their own Sprints. All together we have dozens of Sprints of differents dev projects and a painfull hard work to use only one board to all dev projects. In this case, this plugin dont help me.

How can I filter Sprint just by choosing the "version"? Can I make a kind of linking between Sprint and Version?

Thanks....

Hi everyone,

Just a quick update to everyone interested in Epics & Backlog panels filtering using Jira Software server 7+
To avoid any questions Jira Cloud WON'T be supported by our app.

As part of our latest Agile Board Filter 2.5 release we've added the following filters:

Epics & Versions panels include now:

JQL features

• JQL filtering including a simple JQL editor + JQL autocomplete
• JQL Lock to main filtering bar - use basic view drop-downs to filter the panels or create JQL
• JQL Lock works with Quick Filters - so you can filter the Epics or Versions panels using your Quick Filters
• Filters can be saved as private (only visible to creator) or shared types 
• Search mode - JQL on the epics panel can be executed against epics or issues linked to Epics panel - for example you can find epics using component1 or restrict the epics panel by finding issues using component 1 which are linked to epic panel

Live filtering

• Live search input for fast text search - by project key, name or key
• Predefined filters: Empty, Non-empty, Completed, Uncompleted, Estimated, Unestimated.
• Predefined filters are "intelligent". For example you'll be able to select Empty & non-empty and restrict the result to estimated. They will not exclude each other as Quick filters would do.
• Sync to issues - Epics or Versions panels will be restricted to visible issues right side backlog. For example use a Quick Filter to show bugs and the panel list will show Versions related to visible bug tickets.
• Estimate - MIN, MAX - to find overestimated, underestimated issues - works with any estimation statistic, and accept time format for example 2d 3h

New options:

• By default filtered out items will be hidden - navigating through the version list will hide filtered out Epics to simplify navigation. Both panels have a Show filtered out items options to restore the original behaviour.
• Include epics for selected version - if an Epic is directly linked to a version it will not be filtered out (hidden) from the epics panel list. That is useful if you assign epics to versions.
• Show workflow label on the Epics panel to see which epics are in Done status. Such epics could be easily identified and Marked as Done or reopened if some issues are still in progress. 
• Show version label - this label will allow to identify Epics directly linked to a version.

Additionally filters and options are:

• persistent, so after board refresh they will be automatically loaded
• sections can be collapsed / expanded to save space
• a build in help is located under question marks

For any questions please contact us directly on support@extensi.io

All the best

eXtensi team

This works at least for me if you switch from the default board of the project containing all Epics (e.g. MyProject Requirements) to a board having a filter like "component = MyComponent". The Epic pane is filtered accordingly then, only showing Epics of MyComponent. (Jira Server 7.5)

The list of epics remains static, no matter if filtered by components. The list of epics (+ideally versions) should be changing based on "Quick Filters" feature.

Maybe this has been mentioned before: the Epic pane is actually filtered when components are added to Epics and a board filtered by component is used.

Would definitely be great to see that in the near future. For enterprise level scrum planning across a program this is essential.

So +1 for getting this into Jira soon.

This is a very frustrating issue - I agree not having this feature is a bummer.  

However, my only work around is to not use the Team board and thumb through multiple project boards instead which is very time consuming.

This issue just got put on the backlog.  We all know what doesn't happen next... 

I don't even use the Scrum boards anymore, I have scores of Epics appearing, making it useless...

Booooo 

Hi everyone,

Thanks for your interest in this issue.
This request is considered a potential addition to our longer-term roadmap.

We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

• Performance and stability improvements
• Archiving projects for improved performance
• Optimising the use of custom fields
• Improving performance of boards
• Improving Jira notifications
• Allowing users to edit shared filters and dashboards
• Mobile app for Jira Server

You can learn more about our approach to highly voted server suggestions here.

To learn more on how JAC suggestions are reviewed, see our updated workflow for server feature suggestions.

Kind regards,
Jira Server Product Management

Any update on this? We are wanting some filtering capabilities for epics as well. For what it is worth, I would vote this to be a great added feature!

In next couple of releases we plan to improve epic\version panel filtering.

Please share all your ideas or add feature requests here:

https://community.atlassian.com/t5/Product-Apps-discussions/Epic-Version-Panels-filtering-features/m-p/629901#M64

All of you have not considered another important problem related to this issue:

What about having 2 projects on the same board/team ? If I define a quick filter for my board to work on one project only, still I will see all the epics for both projects !!

Thank you,
S.

Hi @David Varga

The issue is the concept of Quick Filters not related to our plugin.

1. Filter out epics using the same JQL used by Quick Filters (or our plugin)
We or Atlassian would have to introduce some sort of checkbox - "Apply issue QuickFilters to the epic\version list panel" 
Let's say you'd like to filter out issues by Component 'X'. Used JQL (Quick Filters) would hide epics without Component 'X'.
That would give unexpected and confusing results to the end user.

2. Checking epic links between Issues and Epics
That would require another checkbox - "Hide epics not linked to visible issues on the backlog" 
Such relationship couldn't be checked using the Quick Filter JQL used to filter out the issue list.
That would require a custom JQL calls but we were not able to find any function to return all epics from a list of issues.

You said " show only epics, that are linked to the resulting issues".
What is the actual use case here? 
Could you give an example how this would be used?

Best Regards
Przemyslaw

Aggree, quick filters should also apply to Epics and Versions list. (ie. show only epics, that are linked to the resulting issues) Or at least should be a board configuration parameter, where it is adjustable.

Or @Przemyslaw Chudzinski [extensi.io] would you be able to implement something similar in your plugin?

Thank you.

We have a couple of filters which perfectly apply on the stories / issues in the backlog.

However, they don't work for the list of epics

This is very annoying and we dont use the list of epics anymore but since then the backlog is a mess!

Please make sure filters appliy on the whole board - as well on the list of epics

We sometimes have 20-30 Epics running at the same time and want to view a certain Epic in the board and where we are. The best solution for us would be to have a similar solution as for the backlog where you can select a certain Epic and only that specific Epic is shown in the board.

Cheers,
Lars

What about resolved epics?

What would you say for a tickbox "Hide resolved epics"?

Cheers

Przemyslaw

Have the same issue. This would really help us when managing our projects.

Thanks!
Lars

We would also find the ability to more easily sort or filter the list of epics in the Epic panel on a board more efficiently.  We often end up with a difficult to manage number of epics associated with our long running project, and there isn't a good interface for focusing on just those that are relevant to a particular release.  I know that I can grey out the currently irrelevant epics by applying a filter from the 'Version' panel, but these are often still spread through a large list, and we would like to be able to actually hide the greyed out items, or at the least to sort the list of epics based on version so that they all appear together in the list.

Thanks!

We'd like to see this, too.

Hi, any  suggestions or feature requests for the Agile Board Filter Epic\Version Filtering send on support@extensi.atlassian.net.

@Peter - yes it can be done - check your email.

Hi @przemyslaw , the filter for the Versions works, but it is not possible to catch the Project ID. It means, i can't filtering the short name of the project. For example, i have a few projects with the Version B-Muster, see the picture. When i filter for "B-Muster", it shows all B-Muster and i can't choose the spezifical project.

Hi lcash, we could do that, but that would require a lot of development. 

Hi pch728661396,

Can you insert JQL in the search field for the Epic? 

For example: would it be possible for me to filter Epics based on their component by typing "component in ([list of components])"? 

Thank you.

Lee

Please add this for JIRA Cloud asap!