0004133: "Summary stats are links to filters for view_all_bugs" feature is broken - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0004133	mantisbt	filters	public	2004-07-19 12:42	2004-08-29 02:02

Reporter	mmchenry	Assigned To	jlatour
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	0.19.0a2
Fixed in Version	0.19.0rc1

Summary	0004133: "Summary stats are links to filters for view_all_bugs" feature is broken
Description	The new feature introduced in 0.19.0a1 0003737: Summary stats are links to filters for view_all_bugs seems to be broken in 0.19.0a2. Always lists all bugs instead of filtering to the critera of the specific summary link.
Steps To Reproduce	Click any of the stat links on the summary page.
Additional Information	I'm pretty sure this was working correctly in 0.19.0a1, but have not gone back to confirm this.
Tags	No tags attached.

thraxisp 2004-07-19 14:12 reporter ~0006149	I can't seem to reproduce this on my private installation, not on bugs.mantisbt.org. Are you in a single project, or "All Projects"?

mmchenry 2004-07-19 17:26 reporter ~0006155	Went back to verify thraxisp's question and now it seems to be working! I messed around with this for at least 15 minutes this morning and it definitely was not working. Every link on the summary page returned all bugs. Now it's working as expected. I did notice, however, that the issue still exists on http://bugs.mantisbt.org. This morning I was bouncing back and forth from my private test site to bugs.mantisbt.org checking out the issues in the changelog for 0.19.0a2. I can't say for sure now if noticed the issue on my installation or on bugs.mantisbt.org. In any case it seems to be fine on my installation now. Is this expected behavior on bugs.mantisbt.org?

hennot 2004-08-05 15:50 reporter ~0006663	It seems to me that this issue temporarily vanishes if the user changes the current project... until the next login.

jlatour 2004-08-06 09:57 reporter ~0006698	I can seem to reproduce this on one installation (not on this one). I'll see if I can pinpoint the cause.

jlatour 2004-08-06 10:34 reporter ~0006701	OK, I think the problem was that the user did not have a filter cookie, and without a filter cookie it wouldn't even consider the filter in the URL.