Dear all,

I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

Sincerely,
Aakrity Tibrewal
Jira DC

This would be an amazing feature to have prioritized in your product backlog. We want our execs to start using this to track their projects but it's super annoying to have the settings reset after every refresh.

For enterprise customers this is a vital functionality to have. In complex setups with thousands of issues, distributed on numerous teams projects and initiatives one of the biggest problems is to actually get a view on the issues you want to see. Users tend to use custom fields in order to sort out the issues in different aspects. 

As all other Jira functionality such as boards, dashboards, SLA:s are supporting JQL and filters, users expect to have this functionality in Portfolio as well. I would say that this is one of the major showstoppers for many larger customers to use Portfolio. 

@aprilBrotherson I don't use JQL as it can't do it!   I extract the entire project portfolio into Excel then plot current work done against the total estimate, month on month. 

@pauljones would you mind sharing your jql for a burn up?  I've been searching aimlessly trying to find a reference!

Having JQL would make a great difference especially as we are limited to 2000 entries - the current filtering means it is really hard to work around the limits for a large project (I use the data for a burn up)

Agreed, better filtering is required. Either JQL or filtering by available columns but it is much too restricted at the moment.

Either would work for us, we really just need some way to quickly filter on custom fields that have been included in the plan. I do think the JQL option would provide the most flexibility.

Hi 

i agree totally Anthony and Jeff. If is similar to filter functionality within the add-on structure by ALM Works, it would be create.

Anthony, thanks for the ticket. 

A JQL Quick filter would be fine (MVP) but I would prefer drop downs like you provide for Projects, Releases, Teams - for custom fields. We use a multi-value field for Market Segment and it is very important to be able to filter our master roadmap for one or more of those. Aha let me add filterable fields to that row. Love the tighter integration but miss that critical filtering ability.