Skip to content

Mantis Bug Life Cycle anpassen

Wenn man einen Workflow für sein Team gefunden hat, so muss man diesen natürlich auch entsprechend im Bugtracker anpassen. Ich selber nutze seit Jahren, bei meinen Projekten die ich begleite den Mantis Bugtracker.

Hier stelle ich einige Beispiele zusammen wie man einen entsprechenden Workflow einfach und effektiv einbinden kann.

Weitere Informationen zu den Änderungen findet man auch hier.

http://www.mantisbt.org/manual/manual.customizing.mantis.customizing.status.values.php

Die Datei config_inc.php befindet sich im Mantis Root Verzeichnis


################################
# Mantis Look and Feel Variables
################################

# Workflow Mantis by Frank Rentmeister
$g_status_enum_string =   ’10:new,20:feedback,30:onhold,40:dispatcher,50:assigned,60:qa,70:running,80:passed,90:closed’;

# Status color additions /Definition Farbe
$g_status_colors[‘new’]          = ‘#ffa0a0’;
$g_status_colors[‘feedback’]       = ‘#ff50a8’;
$g_status_colors[‘onhold’]          = ‘#ffd850’;
$g_status_colors[‘dispatcher’]       = ‘#c2a8d4’;
$g_status_colors[‘assigned’]       = ‘#8E83DF’;
$g_status_colors[‘qa’]             = ‘#B0C4DE’;
$g_status_colors[‘running’]       = ‘#ffffb0’;
$g_status_colors[‘passed’]          = ‘#cceedd’;
$g_status_colors[‘closed’]          = ‘#e8e8e8′;

# Kompletter Workflow: Hier wird festgelegt für welche Bereiche wir für den Workflow definieren

$g_status_enum_workflow[NEW_]         =   ’50:assigned,20:feedback’;
$g_status_enum_workflow[FEEDBACK]       =   ’50:assigned,40:dispatcher,60:qa,30:onhold’;
$g_status_enum_workflow[ONHOLD]       =   ’20:feedback,40:dispatcher,50:assigned,60:qa’;
$g_status_enum_workflow[DISPATCHER]      =   ’20:feedback,50:assigned,60:qa,80:passed,90:closed’;
$g_status_enum_workflow[ASSIGNED]       =   ’60:qa,40:dispatcher,20:feedback,30:onhold’;
$g_status_enum_workflow[QA]          =   ’70:running,20:feedback,30:onhold,50:assigned’;
$g_status_enum_workflow[RUNNING]       =   ’80:passed,20:feedback,40:dispatcher,50:assigned,60:qa’;
$g_status_enum_workflow[PASSED]       =   ’20:feedback’;
$g_status_enum_workflow[CLOSED]       =   ’20:feedback’;

Änderung in der custom_constant_inc.php

Die Datei custom_constant_inc.php muss im Root Verzeichnis des Mantis Bugtracker erstellt werden.Danach diesen Code Block integrieren.

/*
* Created on 09.08.2008
*
* Workflow Änderungen/ Mantis
* By Frank Rentmeister

* ALT: ’10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved,90:closed’;
* NEU: ’10:new,20:feedback,30:on hold,50:assigned,60:qa,70:running,80:passed,90:closed’;
*/

define ( ‘ONHOLD’, 30 );
define ( ‘DISPATCHER’, 40 );
define ( ‘ASSIGNED’, 50 );
define ( ‘QA’, 60 );
define ( ‘RUNNING’, 70 );
define ( ‘PASSED’, 80 );
define ( ‘CLOSED’, 90 );

Änderungen in der custom_strings_inc.php

Die Datei custom_strings_inc.php befindet sich im Root Verzeichnis des Mantis Bugtracker.

# --------------------------------------------------------
# Modifikation eingebaut von Frank Rentmeister am 17.08.2008/ Für Task "Customizing Status Values"
# --------------------------------------------------------

$s_status_enum_string =   ’10:new,20:feedback,30:on hold,40:dispatcher,50:assigned,60:to qa,70:test is running,80:passed qa,90:closed’;

$s_hierarchy_link = ‘Mantis Hierarchy’;
$s_hierarchy_project = ‘Projects’;
$s_hierarchy_description = ‘Description’;

###############################
# Failed
###############################
$s_failed_bug_button = “Issue is failed “;
$s_failed_bug_title = “Set Issue Ready to failed”;
$s_email_notification_title_for_status_bug_failed =
“The following issue is FAILED.”;

###############################
# Test is Running
###############################
$s_running_bug_button = “Issue is ready for running test “;
$s_running_bug_title = “Set Issue Ready to running test”;
$s_email_notification_title_for_status_running =
“The following issue is running into a TEST.”;

###############################
# QA
###############################
$s_qa_bug_button = “Issue is ready for QA-Test “;
$s_qa_bug_title = “Set Issue Ready to QA-Test”;
$s_email_notification_title_for_qa =
“The following issue is going into QA.”;

###############################
# Passed QA
###############################

$s_passed_bug_button = “Issue passed qa “;
$s_passed_bug_title = “Set Issue Ready to passed qa”;
$s_email_notification_title_for_status_bug_failed =
“The following issue is PASSED QA.”;

###############################
# On Hold
###############################

$s_onhold_bug_button = “Issue is on hold “;
$s_onhold_bug_title = “Set Issue Ready to on hold”;
$s_email_notification_title_for_status_onhold =
“The following issue is ON HOLD.”;

###############################
# Dispatcher
###############################

$s_dispatcher_bug_button = “Issue is for dispatcher “;
$s_dispatcher_bug_title = “Set Issue Ready to dispatcher”;
$s_email_notification_title_for_status_dispatcher =
“The following issue is for DISPATCHER.”;

?>

Post a Comment

Your email is never published nor shared. Required fields are marked *