View Issue Details

IDProjectCategoryView StatusLast Update
0010779mantisbtbugtrackerpublic2010-02-22 14:34
ReporterSL-Gundam Assigned Todhx  
PrioritylowSeveritytweakReproducibilityalways
Status closedResolutionfixed 
Product Versiongit trunk 
Target Version1.2.0Fixed in Version1.2.0 
Summary0010779: due date is filled in by default on cloning while in the cloned report it was empty
Description

When i try to clone a bug report where the due date is not set, mantis automatically fills in "1970-01-01 01:00" as the due date in the form while your cloning.

I also receive 2 notice level errors about f_due_date

It seems mantis needs to check whether this value is set before using it as a value in the form

TagsNo tags attached.
Attached Files
bug_report_page.patch (1,098 bytes)   
From 3d2923de53f2cf7a359be204f7a2b610e9fbca16 Mon Sep 17 00:00:00 2001
From: Frank Rodgers <frodgers@redcom.com>
Date: Wed, 18 Nov 2009 09:07:26 -0500
Subject: [PATCH] Report Due date was set to Unix Epoch for Cloned reports.

Regardless whether Cloned ticket Due date was set.
Due date is now inherited from Cloned ticket.

diff --git a/bug_report_page.php b/bug_report_page.php
index 66c3447..2ac3795 100644
--- a/bug_report_page.php
+++ b/bug_report_page.php
@@ -89,7 +89,7 @@
 		$f_steps_to_reproduce	= $t_bug->steps_to_reproduce;
 		$f_additional_info		= $t_bug->additional_information;
 		$f_view_state			= $t_bug->view_state;
-
+		$f_due_date				= $t_bug->due_date;
 		$t_project_id			= $t_bug->project_id;
 	} else {
 	    access_ensure_project_level( config_get( 'report_bug_threshold' ) );
@@ -230,7 +230,7 @@
 			<select <?php echo helper_get_tab_index() ?> name="priority">
 				<?php print_enum_string_option_list( 'priority', $f_priority ) ?>
 			</select>
-			<?php } else { 
+			<?php } else {
 			   echo get_enum_element( 'priority', $f_priority );
 			} ?>
 		</td>
-- 
1.6.0.4

bug_report_page.patch (1,098 bytes)   

Activities

frodgers

frodgers

2009-11-18 09:23

reporter   ~0023749

I have uploaded a patch that will inherit the Due Date from the Report being cloned. This value was not being set so it defaulted to the Unix Epoch.
I didn't see the any errors regarding f_due_date, so this may only fix part of the issue.

dhx

dhx

2010-02-18 00:22

reporter   ~0024409

Thanks for the patch. I hadn't seen this issue until now, so I've committed the fix to both 1.2.x and 1.3.x branches.

Related Changesets

MantisBT: master-1.2.x 17c46c7c

2009-11-18 09:07

frodgers

Committer: dhx


Details Diff
Fix 0010779: Due date set to Unix Epoch for cloned reports

Regardless of whether the source of a cloned ticket had a due date set,
the new cloned ticket was always given a due date equal to the Unix
Epoch.

This patch ensures that the due date is inherited from the source of the
cloned ticket.

Signed-off-by: David Hicks <hickseydr@optusnet.com.au>
Affected Issues
0010779
mod - bug_report_page.php Diff File

MantisBT: master 8e803c3b

2009-11-18 09:07

frodgers

Committer: dhx


Details Diff
Fix 0010779: Due date set to Unix Epoch for cloned reports

Regardless of whether the source of a cloned ticket had a due date set,
the new cloned ticket was always given a due date equal to the Unix
Epoch.

This patch ensures that the due date is inherited from the source of the
cloned ticket.

Signed-off-by: David Hicks <hickseydr@optusnet.com.au>
Affected Issues
0010779
mod - bug_report_page.php Diff File