Hi @daveaust,
A higher hierarchy level or calculated members is recommended way to get sub-total or aggregated value. But this is not going together when a dimension is also on report pages and used as a multi-selection filter.
In this case, consider working with sprint boards on report rows and pages. When more details are needed, the user can interact with the report and expand the board to the sprint level.
Another option is to create a new calculated member in the Sprint dimension that would group specific sprints. For example, recently closed sprints or sprints matching specific name patterns, or handpicked lists with sprints. In this case, the Sprint dimension is on report rows only (remove Sprint from pages).
More details on calculated members are described here: Calculated members in other dimensions. And eazyBI Demo account has several Sprint grouping examples: Issues - Jira Demo - eazyBI
Best,
Zane / support@eazyBI.com