Epic\Version Panels filtering features Edited

We've already released some cool Epic\Version lists features:

  • Live search by Epic\Version name and by Project key
  • Unestimated (epics\version having unestimated tasks)
  • Uncompleted (epics\version having including open tasks)
  • Non-Empty (hides epics\versions without any tasks)
  • Empty -(only shows epics\versions without any tasks)
  • The cards on the panel will show the current workflow status
  • Sync to issue 








New features comming soon:

  • Filter by story points (min, max)
  • Filter by version dates (from, to)
  • JQL filtering including: ability to save/load filters, lock to backlog filter, full JQL and autocomplete support


Any other ideas/requests?






eXtensi CEO


I really like the four Epic filters you've done there.

Probably a little bit of overkill, but also I find myself filtering for unusual Epic sizes as well as unestimated.  Imagine you've got 50 epics, with a mean average size of 100 story points.  An average doesn't tell me much, I'd like to be able to pull out the epics that have 500 points or 3 points.  Items that are a long way off the average probably need attention.

Also, Epics with flagged issues would be handy for chasing up blockers.

Nice ideas thank you.

What do you think to move all the possible options to board configuration. So a team(per board)\jira admin (globally)\user could choose what kind of filters should be visible?


PS. chackout the demo




I think the board admin would naturally look to the board configuration for this.  Good idea!

Add the capability to SHOW only epic that are "result" of the current quickfilter selection

@fabrizio galletti

But that would filter the epic list using a JQL.

Issues in the backlog and epic list would be limited the same way. 


For example: 

Let's say story issue type would use components and epics not (no component field at all for issue epic type).

In such scenario a quick filter "components in..." would hide all epics on the panel and show issues on the backlog list only.

That would be a mess!!!

Have you considered this?

What is your use case?

A nice way to do this might be to have one of the checkboxes be "Apply Board filter", so the user has the option to apply the same filter or not. 

Another approach might be to allow having the Filter text box in the "epics" panel actually be a full JQL text filter (advanced), so user has full flexibility and can copy-paste the board filter (advanced mode) to the epic or version panel. 

Best might to have JQL text box, as well as the "Apply board filter" check box. That way user can use the same filter as the board (and not have to copy paste it), or override it with a different filter, as needed for the situation.  

A use case I can think of will be:

I want to see all the Epics and backlog for a particular "Customer" value. Both epics and stories have Customer field. I can apply the "Customer" filter to the board and quickly see only the epics and stories that affect that particular customer. 

Hi @Lalit Mehta

The JQL input seems to be reasonable.

Maybe a JQL icon that would switch the input from live search to Full JQL mode an the othe way around.

The checkbox hmmm.. may be usefull in such scenario.

So I'd say if you are in Advanced mode and checkbox is selected the field should be read only and every time you use the Agile Board Filter the Epic JQL field should be updated automatically. 

Keep in mind that Live Search is super fast and JQL mode will be slow.

@Przemyslaw Chudzinski [extensi.io] i was thinking....


Sometime i've noticed that for large team organization you need to filter not only the story but the list of epic too..

This in my vision can be done in 2 different ways:

- Show only the epic resulting in the current filter selection: starting from the quickfilter, get the list of epic that are used by the story filtered 

- Apply the same filter to epic..


In my experience the first one can help a lot, the second one can create a lot of misunderstanding so a different way to filter epic should be fine. I like the proposal of a "jql" filter 

Hi @fabrizio galletti

So your first option would be something like:

- Restrict the list of epics only to Epics linked to displayed issues 


Is that correct?

Yep, but in order to have this working after that we need some kind of "lock" so we can change the filter and epic remain in list..


sound complicated. It's a proposal, right now it's impossible to have a decent plan on this dashboard, hope you figure out a good solution

@fabrizio galletti

The feature has been added and its called Sync to issues

JQL including lock is coming next :)

The filtering shown on the screen has been released.

Right now we're looking at some new filters and improvements.

Stay tuned and bring all ideas to us.
Even the craziest one! We'll do it.

I find the link between the selection version and epic a bit confusing. It seems that the epic's version is based on the versions of the issues within it. But if the epic has an explicit version that value is ignored. 

This makes it hard to use this view to plan out a few versions where the epics have already been allocated to the versions. For example, if I have three version and a few dozen epics, with no issues yet, each assigned to one fo the three versions, when I select a version all of epics are dimmed -- including the epics with the selected version.

Hi @Barry Kaplan,


Soon we're going to release a full JQL filtering of Epic / Version panels and I think that is going to resolve your use case.

You'll be able to filter out epics by version using the JQL mode and the tickets using the Filtering Bar.  

That way you'll not have to select individual versions on the panel.




Anyway that is an interesting idea to introduce some kind of "unlock" icon that would disable epic filtering while navigating through the version panel. I'll add it to our backlog.





Is this new filtering going to be released for Kanban too?



Waiting for a Customized JQL Filter on the Epic Panel. !! 

We would like to group our Epics  (depending on their Status) with custom JQL Filters on Epic Panel. Hope with the next release this case will be solved. 

Thanks in advance!


- PreetiD

Hi everyone we've released sync to issue feature

More details and examples here



Log in or Join to comment
Community showcase
Teodora [Botron]
Published Feb 15, 2018 in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

1,134 views 6 19
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot