Custom status in Mantis Bug Tracker
Asked Answered
Y

2

6

I want to add a custom status to Mantis Bug tracker called "On Hold". Following some blogs I found online, I added the following lines to config_local.php:

$g_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,55:onhold,80:resolved,90:closed';
$g_status_colors['onhold'] = '#cceedd';
$s_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,55:onhold,80:resolved,90:closed';

However, when I go to assign this status to a bug, it displays as @55@ in the drop down.

Any ideas why this might be?

Yahoo answered 9/5, 2012 at 21:2 Comment(0)
A
6

See the Mantis reference on customising status values:

Define a constant to map the new status to.In a new file custom_constants_inc.php in the main mantisbt directory:

<?php define ( 'TEST', 60 ); ?>

Define the language strings required. This may need to be defined in several languages.In a new file custom_strings_inc.php in the main mantisbt directory:

<?php
$s_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned, 60:to be tested,80:resolved,90:closed';
$s_to_be_tested_bug_button = "Issue Ready to Test";
$s_to_be_tested_bug_title = "Set Issue Ready to Test"; 
$s_email_notification_title_for_status_bug_to_be_tested = "The following issue is ready TO BE TESTED.";
?>

Define any configurations required.In the existing file config_inc.php in the main mantisbt directory:

$g_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned, 60:to be tested,80:resolved,90:closed'; # Status color additions
$g_status_colors['to be tested'] = '#ACE7AE';                            

Add the status to any workflow defined in config_inc.php.

Anatto answered 10/5, 2012 at 8:41 Comment(2)
Thanks for the response. Making the changes you suggested appears to have fixed the problem.Yahoo
@Xenos - that link is outdated, but not sure why I linked to mantisforge ... update link to mantisbt.org, thanks!Anatto
Z
1

I am using MantisBT version 2.1.0 and had the same problem. The fix for me was to move the files custom_constants_inc.php and custom_strings_inc.php from the main mantisbt directory to the config directory.

Zinciferous answered 23/2, 2017 at 4:48 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.