Quite frustrating that you're discouraging us to use Manual Breakdowns & Bucket Groups when we're only forced to use such methods because of the inherent limitations of PA, eg the inability to readily create Automated Breakdowns on String fields and the inability to perform ad hoc grouping of Breakdown Element scores (the latter being the biggest customer ask need and it still hasn't been delivered, only a botched effort in the New York release).
Bucket Groups by themselves or used for bucketing date-based data (like age of backlog) are fine to use but we don't want to use them for arbitrary groups (when they are similar to Manual Breakdowns). Using manual breakdowns is just robbing you from using that data in other places and costs a lot in terms of performance. It is available as an option, but it rarely a good option for a production process.
@@adamstout259 I totally agree but my point is that in our organisation bucket groups for bespoke groupings is often an easier solution than changing our data model, but we wouldn't have to resort to either of multi-element select had been properly implemented.
Quite frustrating that you're discouraging us to use Manual Breakdowns & Bucket Groups when we're only forced to use such methods because of the inherent limitations of PA, eg the inability to readily create Automated Breakdowns on String fields and the inability to perform ad hoc grouping of Breakdown Element scores (the latter being the biggest customer ask need and it still hasn't been delivered, only a botched effort in the New York release).
Bucket Groups by themselves or used for bucketing date-based data (like age of backlog) are fine to use but we don't want to use them for arbitrary groups (when they are similar to Manual Breakdowns). Using manual breakdowns is just robbing you from using that data in other places and costs a lot in terms of performance. It is available as an option, but it rarely a good option for a production process.
@@adamstout259 I totally agree but my point is that in our organisation bucket groups for bespoke groupings is often an easier solution than changing our data model, but we wouldn't have to resort to either of multi-element select had been properly implemented.