Mantis Bug Tracker - Forums

Dear all,

I have tried to customize the status based on the Mantis manual and would like to share my experience.

Mantis Version:
Tried on version 1.1.2

Notes:
1. The status selected are new, assigned, clarifying, ready to test, resolved and closed.
2. The workflow was also in the sequence of the list above.
3. The workflow was customized to allow only next available status to be listed for selection.
4. The customization had removed 3 default status and added 2 new status.
5. Colour associated with status had also been customized.
6. Further customization on status can be made from the "Workflow Transitions" under the "Manage Configuration" in Mantis. Administrator privileges are required

Customization steps:
1. Rename customization file "config_inc.php" to "custom_config_inc.php" in the main "mantis" directory.
> mv config_inc.php custom_config_inc.php

2. Create a new "config_inc.php" file in the main "mantis" directory. It should contain the following lines only.
<?php
require_once('custom_config_inc.php');
?>

3. Create the file "custom_constant_inc.php" in the main "mantis" directory.
<?php
# Customized new status
define ('CLARIFY', 60);
define ('TEST', 70);
?>

4. Create the file "custom_strings_inc.php" in the main "mantis" directory. It should contain the following lines. If the file also exists, add the following lines to the end of the file.
<?php
# Customize workflow status
$s_status_enum_string = '10:new,50:assigned,60:clarifying,70:ready to test,80:resolved,90:closed';

# Customize status Clarifying
$s_clarifying_bug_button = 'Clarifying';
$s_clarifying_bug_title = 'Set Issue to Clarifying';
$s_email_notification_title_for_status_bug_clarifying = "The following issue is clarifying";

# Customize status Ready to Test
$s_ready_to_test_bug_button = 'Ready to Test';
$s_ready_to_test_bug_title = 'Set Issue Ready to Test';
$s_email_notification_title_for_status_bug_ready_to_test = "The following issue is ready to test";
?>

5. Modify the file "custom_config_inc.php" in the main "mantis" directory. This file should have been created by the first step. Add the following lines to the end of the file.
# Customize status & workflow
$g_status_enum_string = '10:new,50:assigned,60:clarifying,70:ready to test,80:resolved,90:closed';

# Customize next available status in workflow
$g_status_enum_workflow[NEW_] = '10:new,50:assigned,60:clarifying';
$g_status_enum_workflow[ASSIGNED] = '50:assigned,60:clarifying,70:ready to test,80:resolved';
$g_status_enum_workflow[CLARIFY] = '50:assigned,80:resolved';
$g_status_enum_workflow[TEST] = '50:assigned,80:resolved';
$g_status_enum_workflow[RESOLVED] = '50:assigned,70:ready to test,90:closed';
$g_status_enum_workflow[CLOSED] = '50:assigned';

# Customize status colors
$g_status_colors['new'] = 'white';
$g_status_colors['assigned'] = 'pink';
$g_status_colors['clarifying'] = 'yellow';
$g_status_colors['ready to test'] = 'orange';
$g_status_colors['resolved'] = 'lightgreen';
$g_status_colors['closed'] = 'gray';


Hope the above could help.

Regards,
Francis

Hi, I use this configuration for my custom statuts, but I have a problem when there is a relationship with two or more tickets of two different projects, when the user examines one of the two and the status of the other is not supported in the project that the first belongs to, the status is presented as a @nn@ (nn is the key of the status) instead as the appropriate name.
It is requested to present always the name of the status, independently of it is a valid status for the current project or not.
Also, the custom colors not appear in subprojects.
Do you know what is the cause of these problems?

Thanks.

Dear mauro,

Pls provide more details of your problem. Thanks.

Regards,
Francis

Hi Francis,
thanks for your reply.
I solved the problem, it was a problem in the Manage Projects.
The problem was on the $s_status_enum_string variable, because we wanted one definition for each project but the child projects without the status defined in the father project (with the $s_status_enum_string variable) can't see the strings associated to the father project. Then, we used the customize $s_status_enum_string variable for all projects with all possible status.
Thanks again and good guide.

Regards, Mauro.

Dear mauro,

I have been very busy recently and spent very little time on Mantis. But, really glad to hear your problem was resolved.

Regards,
Francis

hi all!

i ve a problem that i should always edit config_defaults.icn and strings_english.txt files.Mantis doesnt look at the config_inc file... anyone have an idea? m using mantis v 112 by the way.

Thanks the above tips are worth looking at. I'll give a try