Provide more complex and cross-domain filters in DNG (and other domains)

Based on demo about upcoming "ancestor & descendants" filtering enhancement:We want to use the ELM product in the way of "single source of information" - every piece of information to be stored where it belongs to (and only once). To achieve this goal, complex and cross-domain filtering is essential.
It is probably not a good idea to rebuild such complex filter scenarios in every domain again, but what about reusing report builder results in the background to establish such filters? In general the capability is already in report builder (with some gaps), but it also needs to be easily accessible from within the domain UI - similar to the current filters.

Establish complex & cross-domain filtering in all domains by reuse of report builder in the background.
Integrate this background functionality in a very user friendly way (build a report in an integrated UI which already removes some complexity as e.g. PA filter is already given by the current PA and e.g. associations of this PA; current config for running the report is already given by the currently selected config; also: only attributes from current environment and their actual name should be displayed)
Enhance LQE to hold all necessary data to establish such complex reports, like
- Module structure of DNG (to filter e.g. ancestors of certain type)
- Links to/from files
- Links to/from architecture elements

Some complex filter use case examples (artifacts as well as config items):
- All requirements that are linked to a work item planned for a certain iteration or with attribute value xyz
- All requirements with failed test results and open Defects planned for xyz
- All requirements linked to a certain architecture element
- All changesets generated since BL xyz not linked to a work item (or linked to work item planned in iteration xyz)
- All requirements which are satisfying a requirement that is linked to a successful test result

In addition, it would be helpful (at least in DNG) to have an option to decouple the "layout" definition from the view / filter. There are use cases where it is helpful e.g. providing some general views with or without filter but defining the necessary attributes. But there is also often the case that you defined which attributes you need to see, but then want to apply an existing filter which then overwrites the previous settings.