Filters behavior needs to be aligned to Columns and Sorting

What is the challenge?

• Consider a report with Columns Feature Name, Feature Release Name, Epic Name, Epic Release Name. The report works as needed itself. But let us try to add the Filters.

• In Filters I can add all I need for Feature and Epic fields — but when I go for Release Name, I am unable to specify whether the filter should run on Epic’s Release or on Feature’s Release.

• As Epics are typically covering a set of Features and thus span more than 1 Release, the Epics.Release != Feature.Release in many cases.

• Filters do not allow me this flexibility and apply only to the Release of the Root object we select for the data report.

• This in turn means that if I build the structure starting from Epic, I get a vastly different picture than if I start building from a Feature.

• And there simply is no way to specify “Epic release A and Feature release B”. This sounds like a strange use case to bring up until you go Advanced and begin to exclude elements, where it is necessary.

• To add insult to injury, Aha is perfectly fine in sorting over those child release object columns — but not filtering.

What is the impact?

• Limits the ability to fine tune the reports.

• This particular case is a complete blocker to produce a specific view for senior leadership (currently done as a PPT table), which was one of the key points why we bought into Aha at all.

Describe your idea.

• Filters should be applied in the same way the columns are organized, and only relate to the objects added to the data set to exclude any ambiguity.

• As the result, I should be able to set filter for e.g. "Feature Release Name", "epic Initiative Name" etc.