I think I've found a bug in Sumstats.
I'm using SumStats in conjunction with the track-backlog and VisualizationPlugin.
I've got a milestone (let's call it "milestone1") with some tickets, and when I call the .../sumstats/query URL I get the results I expected: http://pastie.org/6361592.
However, if I create a new milestone with a due date in the future, I start getting a "zeroed" response: http://pastie.org/6361594
Any idea of what might be happening? Might it be some misconception on my part of how it is supposed to work?