Modify

Opened 17 months ago

Last modified 16 months ago

#10899 new defect

Bug on query results

Reported by: FilipeCorreia Owned by: robguttman
Priority: normal Component: SumStatsPlugin
Severity: normal Keywords:
Cc: fcorreia@… 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 (0)

Change History (2)

comment:1 Changed 17 months ago 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

comment:2 Changed 16 months ago by rjollos

  • Description modified (diff)

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.