0003475: Reopen bug to custom status possibility

ID	Project	Category	View Status	Date Submitted	Last Update
0003475	mantisbt	feature	public	2003-12-22 06:39	2004-02-06 16:15

Reporter	~~Wanderer~~	Assigned To	vboctor
Priority	normal	Severity	trivial	Reproducibility	N/A
Status	closed	Resolution	fixed
Platform	Any	OS	Any	OS Version	Any
Product Version	0.18.0

Summary	0003475: Reopen bug to custom status possibility
Description	It light of flexibility $g_bug_resolved_status_threshold added $g_bug_reopen_status_threshold into config and modified bug_reopen() global $g_bug_reopen_status_threshold; ... bug_set_field( $p_bug_id, 'status', $g_bug_reopen_status_threshold );
Steps To Reproduce	N/A
Additional Information	For flexible worlflow and the ability to differentiate initial discussion from failed bugfix this change seems as reasonable add-on
Tags	No tags attached.

vboctor 2004-01-13 13:26 manager ~0004879	Fixed in CVS. Following is the fix description: M config_defaults_inc.php Added $g_bug_submitstatus (default NEW) [Status to assign to the bug when submitted.] Added $g_bug_assigned_status (default ASSIGNED) [Status to assign to the bug when assigned.] Added $g_bug_reopen_status (default FEEDBACK) [Status to assign to the bug when reopened.] Added $g_bug_reopen_resolution (default REOPENED) [Resolution to assign to the bug when reopened.] Added "Status Settings" section in the config file to include the above new configs. M bug_update.php Used $g_bug_assigned_status rather than ASSIGNED. M core/bug_api.php (bug_create) Used $g_bug_submitstatus rather than NEW. (bug_create) Used $g_bug_assigned_status rather than ASSIGNED. (bug_assign) Used $g_bug_assigned_status rather than ASSIGNED. (bug_reopen) Used $g_bug_reopen_status rather than FEEDBACK. (bug_reopen) Used $g_bug_reopen_resolution rather then REOPENED.