Burndown should calculate based on currently selected area

Edit Subject

Thank you for your feedback, I'll add your suggestion to the backlog!

To add a bit more info to this....the burndown chart (and sprint statistics) should not only take into account the current selected area, but the areas under it as well. This makes it a great way to get "rolled-up" burndown charts.

We second this! We have a similar setup and really need this!

This is pretty high in our backlog. Stay tuned!

A related request: if you use multiple teams via Area then you also want to have multiple sprint plannings. So for instance if I commit a sprint then I only want to commit the items that are currently filtered (for team/area).

Currently the sprint information shows everything in the sprint while I am looking at a subset. I guess committing the sprints commits everything on it.

Maybe this is already in the picture.

Any idea when we can have this functionality available? And will there be a new version before november (as we would like to start with TFS and your product in two weeks).

The sprint information (in the iteration list with number of story points and remaining work left) does not take the filter into account!

You're right, the statistics still do not take the filter into account. Statistics are unrelated to the burndown chart and so the work involved to change this behavior was a lot more important. However, it was still high on our backlog and we managed to squeeze it in the next release, version 3.6.

Very cool! Not sure if this is already the case, but 'commit' should also only work on the filtered items

Yes I believe it already works on filtered items. Have you had any issue with this?