Patch for bug 103636: Support specifying a date on which a bug is expected to be resolved; patch by Alexandre Michetti Manduca <michetti@grad.icmc.usp.br>, r=jouni, a=myk.

1 files changed, 4 insertions, 2 deletions

diff --git a/long_list.cgi b/long_list.cgi
index 515f4c226..c3abbafcf 100755
--- a/long_list.cgi
+++ b/long_list.cgi
@@ -63,7 +63,8 @@ my $generic_query = "
     bugs.keywords,
     bugs.estimated_time,
     bugs.remaining_time,
-    date_format(creation_ts,'%Y.%m.%d %H:%i')
+    date_format(creation_ts,'%Y.%m.%d %H:%i'),
+    date_format(bugs.deadline, '%Y-%m-%d')
   FROM bugs,profiles assign,profiles report, classifications, products, components
   WHERE assign.userid = bugs.assigned_to AND report.userid = bugs.reporter
     AND bugs.product_id=products.id AND bugs.component_id=components.id
@@ -89,7 +90,8 @@ foreach my $bug_id (split(/[:,]/, $buglist)) {
                        "bug_severity", "component", "assigned_to", "reporter",
                        "bug_file_loc", "short_desc", "target_milestone",
                        "qa_contact", "status_whiteboard", "keywords", 
-                       "estimated_time", "remaining_time", "creation_ts") 
+                       "estimated_time", "remaining_time", "creation_ts",
+                       "deadline")
     {
         $bug{$field} = shift @row;
     }