Project

General

Profile

Actions

Defect #66

closed

Closed issue not marked as closed

Added by bajs bajs over 17 years ago. Updated over 17 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

In the reports section I don't seem to be able to get any data into the "open" and "closed" columns,
even though I have both opened and closed issues. Seems kinda weird since "total" should be "open"
+ "closed", right?

When I press the magnifying glass for one of the tables I see correct counters, except I also have a status "open"
and "closed" (in addition to "Closed", "New", etc...) which both show zero. These ones
also have no color box next to them.

See screenshot.


Files

issues.png (10.4 KB) issues.png bajs bajs, 2008-02-03 10:50
Actions #1

Updated by bajs bajs over 17 years ago

I've tracked it down to the "closed" => 0 in
views/reports/_simple.rhtml and similar files.

In postgresql you need "closed" => "t"
for true. I'm not
sure what you need for false. "f" wasn't it.

Actions #2

Updated by bajs bajs over 17 years ago

Sorry. It was "f". Unrelated typo.

Do you want a patch for this? I'm not sure how you want to
differentiate database engines, and just changing
"closed"
=> 0 to "closed" => "f" will probably
break mysql support.

Actions #3

Updated by Jean-Philippe Lang over 17 years ago

Right. This problem was mentioned in the forum:
http://rubyforge.org/forum/forum.php?thread_id=14561&forum_id
=7505

It was fixed in rev 551.

Actions #4

Updated by bajs bajs over 17 years ago

Ok. I only searched the tracker before submitting. Thanks.

Actions

Also available in: Atom PDF