Ticket #10899 (new defect)

Opened 3 months ago

Last modified 2 months ago

Bug on query results

Reported by: FilipeCorreia Assigned to: robguttman
Priority: normal Component: SumStatsPlugin
Severity: normal Keywords:
Cc: fcorreia@gmail.com Trac Release:

Description (Last modified by rjollos)

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?

Thanks.

Attachments

Change History

03/01/13 20:16:09 changed by FilipeCorreia

Poking around the source code, I realized that the query knows which milestone to consider based on the referrer. I've used a browser plugin to simulate a referrer to get the query results for the first milestone with and without creating a second milestone:

Results for "milestone1", when only "milestone1" was created: http://pastie.org/6361815

Results for "milestone1", when a future "milestone2" also exists: http://pastie.org/6361817

03/22/13 03:19:43 changed by rjollos

  • description changed.

Add/Change #10899 (Bug on query results)




Change Properties
Action