## Problem Currently we're not allowing to use custom properties for filtering. It can be beneficial for users so we should investigate if we can remove this limitation. ## Desired Outcome Allow to use custom propertied for metrics filtering ## Potential Solution Currently we simply compare property name in the filtering class to theoretically nothing stop us to let users use them. So technically, custom properties can be used for filtering right now. The scope of this issue is to verify: 1. Works as expected 2. Covered by specs 3. Documented 4. Verified and agreed with Data team 5. CLI is sorted ## How to verify <!--How can we verify that the desired outcome has been achieved? The instructions from this section should be used to move the issue from ~“worfklow::verification”.--> ## Further actions needed <!--Any further tasks that need to be completed after the main work of the issue is done, such as announcing the changes or updating documentation.--> <!--This section is optional.--> <!--Make sure to add one of the type labels (as per https://handbook.gitlab.com/handbook/engineering/metrics/#work-type-classification):--> <!--/label ~"type::bug" ~"type::feature" ~"type::tooling" ~"type::maintenance"-->