This idea has been raised in both
GHS-8152 ("Sub-tasks should not be included in Version Report") and GHS-9237 ("Multiple versions in version report"). However, those were each fairly specific requests, so I wanted to create an issue that might cover both of those and more.
So, in addition to the desires stated under those other two issues, I would like to be able to constrain the version report to a filter in order to review "what if" scenarios. For example, if the release date of a version is looking to be in jeopardy, I would like to be able to quickly see what the graph would look like if we only included the remaining items of a particular priority and higher. However, I think this additional filter would still need to be scoped to 1 or more versions, and need to only exclude work that remains in an open state. Since I imagine the historical values of work completed would still need to include all items associated with the versions in order to have an accurate measure of velocity. So, the UI design for this definitely isn't immediately obvious to me, unless it was a multi-select for the version list and the choice of "Quick Filters" that only applied to Open remaining work items.
I guess in the mean time I can temporarily move stories between versions to play with "what if's", but that feels messy.