The Analytics capability needs a lot more polish and attention to detail. The spring release was a big improvement in terms of performance due to the fact that some critical database indexes were added. This finally made the product usable for us as were previously getting timeouts on most of the reports.

Now that that glaring problem has been fixed, there are many other little things (and some not so little) that need to be addressed. Here are just a few.

- Estimate treemap shows stories in red and defects in green.
- Looking at velocity by date range I can hover over a bar and get 12 digits of accuracy in the velocity but no label telling me what date range I'm looking at.
- Many of the pie graphs don't indicate what units are being displayed (count, estimate, detail estimate??). I suspect they are showing counts but then why are they displaying decimal places?

Overall it just feels like there isn't a lot of attention to detail here.

Comments

  • I fully support the "more attention to Analytics" mantra. There's a lot to be desired, e.g. ability to save grid configurations (analytic grids), hiding closed project from the project drop-down, label/name consistency between Analytics and the core app, etc. etc.

  • Yes, I get the feeling that there must not be that many Analytics users. Otherwise there would be more feedback in this area. However, we paid extra for this feature and I think it's a reasonable to expect the same level of quality here as in the main application.

  • Thanks for the feedback. The Summer 2011 release addressed the Velocity by Date Range and Pie Chart issues. On the EstimateTreeMap each box represents a single Workitem (Story, Defect, TestSet). The size of the box is determined by the Workitem Estimate and the color is determined by value selected in the “Color Determined By” dropdown. You can group these items using values in the Group dropdown. The DetailEstimateTreeMap behaves the same, except the size of the box is determined by the Workitems Detail Estimate value.