V2 : estimate session from a query limited to 200 work items

[RafaelKoch]

We tried to circumvent #19 by starting a session from a query but then ran into this limitation. Which is maybe alright in itself, but I would suggest to rather cut off at 200 work items and tell the user rather than doing nothing.

Why? -> There is no really good way to limit a query to a number of results, so You never know if estimate will let You use a certain query.

[cschleiden]

I did not think anyone would estimate that many work items at once :) However, the extension should totally support that.

[jennavy82]

@cschleiden Has there been any update on this? I have a main backlog with over 200 items in it. I want to build 1 query that I will use for the poker sessions (query would be anything with iteration xxxxx/backlog). As items get sprinted, moved in and out etc, the number of items in the backlog query will change, but this is where I want the team to continually story point. Is there a way to bypass the 200 item limit so I do not need to make custom queries with special query limits each time we do a planning session? Or do you have a suggestion on another way for me to accomplish what I am trying to do?