Customizing Status Values
Last Modified: April 18, 2005 07:04AM
|
|
(Any)
|
Description
Status examples
The default is no workflow, where all states are accessible from any others. The following example can be transferred to config_inc.php. The workflow needs to have a path from the statuses greater than or equal to the resolved state back to the feedback state. Otherwise, the re-open operation won't work.
$g_status_enum_workflow[NEW_]=
'10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved';
$g_status_enum_workflow[FEEDBACK] =
'10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved';
$g_status_enum_workflow[ACKNOWLEDGED] =
'20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved';
$g_status_enum_workflow[CONFIRMED] =
'20:feedback,40:confirmed,50:assigned,80:resolved';
$g_status_enum_workflow[ASSIGNED] =
'20:feedback,50:assigned,80:resolved,90:closed';
$g_status_enum_workflow[RESOLVED] =
'50:assigned,80:resolved,90:closed';
$g_status_enum_workflow[CLOSED] =
'50:assigned';
To add a status:
- Define a constant to map the new status to.
In a new file custom_constant_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
if ( lang_get_current() == 'german' ) {
$s_status_enum_string =
'10:neu,20:R¸ckmeldung,30:anerkannt,40:best‰tigt,50:zugewiesen,
60:zu testen,80:behoben,90:geschlossen';
} else {
$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:
$g_status_enum_workflow[NEW_]=
'10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,60:to be tested';
$g_status_enum_workflow[FEEDBACK] =
'10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,60:to be tested';
$g_status_enum_workflow[ACKNOWLEDGED] =
'20:feedback,30:acknowledged,40:confi
rmed,50:assigned,60:to be tested';
$g_status_enum_workflow[CONFIRMED] =
'20:feedback,40:confirmed,50:assigned,60:to be tested';
$g_status_enum_workflow[ASSIGNED] =
'20:feedback,50:assigned,60:to be tested,90:closed';
$g_status_enum_workflow[TEST] =
'10:new,20:feedback,50:assigned,60:to be tested,80:resolved,90:closed';
$g_status_enum_workflow[RESOLVED] =
'50:assigned,60:to be tested,80:resolved,90:closed';
$g_status_enum_workflow[CLOSED] =
'50:assigned,90:closed';
|
User Contributed Notes
Customizing Status Values |
|
freddy0
22-Sep-2004 7:28 |
#207
|
you should add the following line in lang/string_yourlanguage.txt:
$s_email_notification_title_for_status_bug_test = "This bug is now in TEST status"; |
|
haaseg@onefreevoice.com
30-Sep-2004 17:54 |
#218
|
There are two additional lines that needed to be added to your language file(s).
Look for # bug_change_status_page.php
Add:
$s_to_be_tested_bug_title = 'Move Bug to TEST Status';
$s_to_be_tested_bug_button = 'Move Bug to TEST status';
These text lines will appear when you use the Change Status button from the bug view page. The $s_*_bug_title variable is displayed at the top of the table, and the $s_*_bug_button variable is the text that is displayed on the Submit button. |
|
ann.patel@motorola.com
06-Apr-2005 19:08 |
#403
|
| Does any one know how to track the length of time a particular issue remains in a state ? For example, I would like to track how long a defect remains in the assigned state, versus the resolved state, etc. Is their a simple way to do this ? |
|
ben @ NOSPAMmediafirma.com
05-May-2005 10:26 |
#430
|
| I would also like to know how to track time/state |
|
ticaro.valmul@caramail.com
02-Jun-2005 11:31 |
#451
|
I'm studying Mantis to decide wether it meets my company needs.
It seems quite interesting.
Everythings works well, excepts customizing the status.
I've tried what is writen in the manual and the notes but it doesn't work.
I'm using version 1.0.0a2.
I can see the new status in the filter List, but I'm not able to select the to_be_tested status when I update an issue. |
|
dcantor@i-siglo21.com
11-Jun-2005 19:25 |
#464
|
| Check $s_status_enum_string in your language string (lang/strings_xyz.php) |
|
asmoore@edge.net
03-Jul-2005 12:34 |
#496
|
I really like this product. Great job! I am currently using 1.0.0a3 since it allows sub-projects and seems a better fit for me than 0.19.2.
I am trying to get a status for TEST installed. I made the changes mentioned in earlier posts. It seems to work ok, but I did notice one thing that could be added. I do not know how to fix it, since I am not very familiar with php at this time.
From the Workflow Transitions page, the Default Value was New. I want a default of Feedback. When I changed the value, a new screen was quickly displayed that said something about '60 access_change' not allowed. I did not get all of the message.
How do I set this default and fix the access issue?
Thanks, Alex |
|
m4[deletethat]@paris.com
05-Jul-2005 9:49 |
#499
|
I try to ADD a status ("returned" in the way mentionned in earlier posts.
In config_inc.php :
#Declarer les status possibles d'un rapport de bug
$s_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,60:RETURNED,70:to be tested,80:closed,90:refused';
# Status color additions
$g_status_colors['RETURNED'] = '#ACE7AE';
In string_french.txt :
$s_status_enum_string ='10:Création,20:A analyser,30:A valider,40:A réaliser,50:En cours de réalisation,60:Retourné,70:A recetter,80:Clos,90:Refusé';
In custom_constant_inc.php
define ( 'RETURNED', 60 );
But i can't see my returned status in the workflow stting page.
I am so sad !! |
|
mantis@no-sp-am-eraandrsolutions.com
09-Jul-2005 8:53 |
#513
|
I've just completed these steps listed in the manual and it worked fine for me on version 1.0.0a3. The workflow all worked and its all working fine.
If you're having problems, I would suggest to take it slow and steady and not rush through the steps. |
|
James
11-Jul-2005 5:35 |
#514
|
Hi!
I'm interested in customising the status but I have some troubles. First, I'd like to be sure this file 'config_default_inc.php' is the one I must modified. It is mentionned as 'config_inc.php' in the manual but I don't have this file in my mantis directory (nor anywhere else, though!)
So, is it the good one to change?
Thanks for your help,
James |
|
benatdalbydotnet@justusefirstbit.com
13-Jul-2005 13:37 |
#519
|
v0.19.2
I found that you have to follow both the core doco and the user comments to get the full solution - thanks everyone.
custom_constant_inc.php
define ( 'KNOWN ISSUE', 85 );
config_inc.php
$g_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved,85:known issue,90:closed';
$g_status_colors['known issue'] = '#7F68F2';
custom_strings_inc.php
$s_status_enum_string = '10:New,20:Feedback,30:Acknowledged,40:Confirmed,50:Assigned,80:Resolved,85:Known Issue,90:Closed';
$s_email_notification_title_for_status_bug_known_issue = "This bug has been declared a Known Issue";
$s_known_issue_bug_title = 'Move Bug to KNOWN ISSUE status';
$s_known_issue_bug_button = 'Move Bug to KNOWN ISSUE status';
<END MESSAGE> |
|
Wil
05-Sep-2005 11:07 |
#592
|
I want add a status but I don't find the procédure.
Can you give the URL when I can find it ?
Thanks a lot.
|
|
rweiss@sbs.com
10-Oct-2005 18:44 |
#641
|
Is it possible to *remove* issues? I want to remove "Confirmed" and "Acknowledged" and then add "Implemented". All of my attempts have failed (I cannot add Implemented, nor can I remove the other two). Instead of "Confirmed" and "Acknowledged", I get @30@ and @40@.
There seems to be a workflow somewhere that I cannot seem to find.
Thanks!
reinhard. |
|
willick
12-Oct-2005 11:23 |
#643
|
I'm also wishing to remove values from the $s_severity_enum_string to only contain the following values:
'20:trivial,50:minor,60:major,70:crash'
I get the the @10@ and @30#...in my severity dropdown list.
I commented out the
return '@' . $p_num . '@';
...from the utility_api (I have no idea what this is used for) and added an if statement around the following lines of code in the print_api:
if ($t_elem2 != '') {
echo "<option value=\"$t_key\"";
check_selected( $p_val, $t_key );
echo ">$t_elem2</option>";
}
...this seems to work around my issues but is there not another fool proof way? |
|
zaki1NOSPAM@N.O.SPAMhotmail.oom
31-Oct-2005 14:50 |
#691
|
I followed all suggested procedures above about 6 times now here are the results:
*It seems it is impossible ot create a state with value 60 or 70. So I had to skip those vales and use 80 and 90.
*My custom colors and custom strings are not used...(any clue why?!).
Here are my files:
custom_constant_inc.php
=======================
<?php
define ( 'QUALIFIED', 10 );
define ( 'IN_OBSERVATION_DECISION', 20 );
define ( 'TERMINATED', 30 );
define ( 'IN_WORK_ASSIGNED', 40 );
define ( 'SOLVED', 50 );
define ( 'TESTED', 80 );
define ( 'CLOSED', 90 );
# 10: Qualified
# 20: In Observation Decision
# 30: Terminated
# 40: In Work Assigned
# 50: Solved
# 80: Tested
# 90: Closed
?>
custom_strings_inc.php
======================
<?php
$s_status_enum_string =
'10:qualified,20:in observation decision,30:terminated,40:in work assigned,50:solved,80:tested,90:closed';
# Status 10: Qualified
$s_email_notification_title_for_status_bug_qualified = "This issue was Submitted.";
$s_qualified_bug_button = "Submit Issue";
$s_qualified_bug_title = "Submit Issue";
# Status 20: In Observation Decision
$s_email_notification_title_for_status_bug_in_observation_decision = "This issue was put In Observation/Decision.";
$s_in_observation_decision_bug_button = "Put In Observation/Decision";
$s_in_observation_decision_bug_title = "Put Issue In Observation/Decision";
# Status 30: Terminated
$s_email_notification_title_for_status_bug_terminated= "This issue was Terminated.";
$s_terminated_bug_button = "Terminate Issue";
$s_terminated_bug_title = "Terminate Issue";
# Status 40: In Work Assigned
$s_email_notification_title_for_status_bug_in_work_assigned = "This issue was put In Work (Assigned).";
$s_in_work_assigned_bug_button = "Put In Work";
$s_in_work_assigned_bug_title = "Put Issue In Work";
# Status 50: Solved
$s_email_notification_title_for_status_bug_solved= "This issue was Solved and Needs to be Tested.";
$s_solved_bug_button = "Solve Issue";
$s_solved_bug_title = "Solve Issue";
# Status 80: Tested
$s_email_notification_title_for_status_bug_tested= "This issue was Tested and Validated.";
$s_tested_bug_button = "Validate Issue";
$s_tested_bug_title = "Validate Issue";
# Status 90: Closed
$s_email_notification_title_for_status_bug_closed= "This issue was Reviewed and Closed.";
$s_closed_bug_button = "Close Issue";
$s_closed_bug_title = "Close Issue";
?>
config_inc.php
==============
<?php
$g_send_reset_password = 'ON';
$g_show_version = 'OFF';
$g_display_bug_padding = 4;
# Status to assign to the bug when submitted.
$g_bug_submit_status = QUALIFIED;
# Status to assign to the bug when assigned.
$g_bug_assigned_status = IN_WORK_ASSIGNED;
# Status to assign to the bug when reopened.
$g_bug_reopen_status = QUALIFIED;
# Resolution to assign to the bug when reopened.
$g_bug_reopen_resolution = REOPENED;
$g_bug_readonly_status_threshold = CLOSED;
$g_bug_resolved_status_threshold = SOLVED;
$g_auto_set_status_to_assigned = OFF;
$s_status_enum_string = '10:qualified,20:in observation decision,30:terminated,40:in work assigned,50:solved,80:tested,90:closed';
$g_status_colors = array(
'qualified' => '#FF9999',
'in observation decision' => '#FFFFCC',
'terminated' => '#A6F6777',
'in work assigned' => '#CCDDFF',
'solved' => '#D0FFD0',
'tested' => '#99ee99',
'closed' => '#EEEEEE');
$g_status_enum_workflow[QUALIFIED]= '20:in observation decision,30:terminated,40:in work assigned';
$g_status_enum_workflow[IN_OBSERVATION_DECISION] = '10:qualified,30:terminated';
$g_status_enum_workflow[TERMINATED] = '10:qualified';
$g_status_enum_workflow[IN_WORK_ASSIGNED] ='50:solved';
$g_status_enum_workflow[SOLVED] = '40:in work assigned,80:tested';
$g_status_enum_workflow[TESTED] ='40:in work assigned,90:closed';
$g_status_enum_workflow[CLOSED] ='10:qualified';
?>
Any help is appreciated concerning the strings and colors... thanks ! |
|
_star@rambler.ru
16-Jan-2006 7:28 |
#826
|
Hi!
I wont add two statuses - "Fixed" and "Completed". I have updated these files:
config_inc.php:
$s_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed,
50:assigned,80:resolved,90:closed,100:fixed,110:completed';
$g_status_colors['fixed'] = '#c8c888';
$g_status_colors['completed'] = '#c8c8ee';
$g_status_enum_workflow[NEW_]=
'10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,100:fixed,110:completed';
$g_status_enum_workflow[FEEDBACK] =
'10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned';
$g_status_enum_workflow[ACKNOWLEDGED] =
'20:feedback,30:acknowledged,40:confirmed,50:assigned,100:fixed,110:completed';
$g_status_enum_workflow[CONFIRMED] =
'20:feedback,40:confirmed,50:assigned,100:fixed,110:completed';
$g_status_enum_workflow[ASSIGNED] =
'20:feedback,50:assigned,90:closed,100:fixed,110:completed';
$g_status_enum_workflow[RESOLVED] =
'50:assigned,80:resolved,90:closed,100:fixed,110:completed';
$g_status_enum_workflow[CLOSED] =
'50:assigned,90:closed,100:fixed,110:completed';
$g_status_enum_workflow[FIXED_PBL] =
'50:assigned,90:closed,100:fixed,110:completed';
$g_status_enum_workflow[COMPLETED] =
'50:assigned,90:closed,100:fixed,110:completed';
custom_strings_inc.php:
$s_status_enum_string='10:new,20:feedback,30:acknowledged,40:confirmed,
50:assigned,80:resolved,90:closed,100:fixed,110:completed';
$s_email_notification_title_for_status_bug_fixed = "Fixed.";
$s_fixed_bug_button = "Fixed";
$s_fixed_bug_title = "Fixed";
$s_email_notification_title_for_status_bug_completed = "Completed.";
$s_completed_bug_button = "Completed";
$s_completed_bug_title = "Completed";
custom_constant_inc.php:
define ( 'FIXED_PBL', 100 );
define ( 'COMPLETED', 110 );
and.. this don't work..
Please, help me with my problem... |
|
staticATxstaticaDOTcom
14-Feb-2006 18:37 |
#894
|
| Make sure there is no whitespace(CR, LF, SPACE, etc) after the ?> . This got me the first time trying to add custom status and mantis just started returning a blank page. Someone on IRC told me about how to fix it. |
|
Gwen
01-Mar-2006 6:19 |
#907
|
| for _star@rambler.ru, look at your config_inc file. Modify '$s_status_enum_string...' by '$g_status_enum_string...' |
|
isa21493@gmail.com
03-May-2006 6:02 |
#1040
|
Hello,
I see that it is necessary to change the file "custom_contant_inc.php",
but i don't have it
Where is it??? I have constant_inc.php but not "custom_constant_inc.php".
help me please.
thanks |
|
isa21493@gmail.com
03-May-2006 9:16 |
#1044
|
Is it possible to add more than 7 status?
We can use 10,20,30,40,50,80,90
Is there others? |
|
krugar does not like spam at ipsi dot fraunhofer dot de
03-May-2006 11:37 |
#1047
|
this applies to version 1.0.1 (and up, possibly)
please note that any workflow configurations you may have done via the web interface under "Manage -> Manage Configuration -> Workflow Transitions" are stored in the database, not in config_inc.php. per project changes are shown in green, changes you applied to all projects are shown in blue in this interface. if you have tinkered with config_inc.php and are wondering why your changes do not show up, you might want to check the "Manage" web interface and possibly delete (database stored) changes applied there.
hope this saves someone a little time |
|
Velan@nospamvelans.coim
16-May-2006 6:00 |
#1069
|
Thanks to Krugar i could understand the problem.
For the inc files missing, you need to create a new one. |
|
coymeeks@hotmail.com
30-May-2006 11:33 |
#1102
|
Hi,
I added some statuses per the instructions on this page and they seem to be working correctly.
However, the ones that were added will not show up in the "View Issues" list.
Any help would be appreciated. |
|
k.kosters@aia-itp.com
06-Jun-2006 7:33 |
#1114
|
| Your filter probably says "hide closed and above". This means that every status with a number higher than the closed status (by default 90)and the closed status itself, will be hidden. So, you can solve this by assigning a lower number to your new statusses. |
|
catharina_x@hotmail.com
06-Jun-2006 7:36 |
#1116
|
| You probably assigned the new statusses with a number higher than the Closed status. The Closed status and every status with a number higher than the closed status, is hidden by the filter by default. |
|
jonathan.firestone@us.widerthan.com
10-Jul-2006 14:17 |
#1186
|
I know everyone is very busy, but could someone *in the know* clean up/combine the Documentation instructions AND the comments here? It would be nice to see all at once what I really should do in order to do a custom workflow/status.
It would be a great help to the new folks here who have trouble sharpening a pencil without a bowie knife, like myself. |
|
jonathan.firestone@us.widerthan.com
12-Jul-2006 14:39 |
#1192
|
| Sorry about the multiple posts folks. I kept getting an error from the MantisBT server when I submitted it and accidentally re-submitted the same comment several times. Nothing showed up so... |
|
c_rodell@msn.com
23-Jul-2006 23:03 |
#1199
|
WILLICK
I am trying to remove some of the default status entries and followed:
I'm also wishing to remove values from the $s_severity_enum_string to only contain the following values:
'20:trivial,50:minor,60:major,70:crash'
I get the the @10@ and @30#...in my severity dropdown list.
I commented out the
return '@' . $p_num . '@';
...from the utility_api (I have no idea what this is used for) and added an if statement around the following lines of code in the print_api:
if ($t_elem2 != '') {
echo "<option value=\"$t_key\"";
check_selected( $p_val, $t_key );
echo ">$t_elem2</option>";
}
...this seems to work around my issues but is there not another fool proof way?
****** This seemed to work but when I view an issue from our view.php?id=435 and I pick the drop down list for the "Change Status To:" I no longer see the @20@ but I still see the blank spot on the drop down list. So I have the same number of drop down items but now they are completely blank. What do I need to do to remove the blank items from the drop down list? |
|
mcraig88@yahoo.com
29-Aug-2006 17:04 |
#1253
|
Any chance this manual will get rewritten so all of the comments can be compiled into one true answer?
And why the heck isn't all of this configuration stuff stored in the DB? |
|
|
|
dieutorak@yahoo.fr
14-Feb-2007 4:36 |
#1599
|
I add status "refused" in mantis 1.0.6.
It seems work :
* first step :
------------
modify config_inc.php and add new line :
$g_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed, 50:assigned,80:resolved,85:refused,90:closed';
$g_status_colors['refused'] = '#c8c888';
* second step (traduction):
-----------
create file custom_strings_inc.php if it doesn't exist and add it :
<?php
if ( lang_get_current() == 'french' )
{
$s_status_enum_string = '10:nouveau,20:commentaire,30:accepté,40:confirmé,50:affecté,80:résolu,85:rejeté,90:fermé';
$s_email_notification_title_for_status_bug_refused = "Rejeté.";
$s_refused_bug_button = "Rejeté.";
$s_refused_bug_title = "Rejeté.";
}
else
{
$s_status_enum_string='10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved,85:refused,90:closed';
$s_email_notification_title_for_status_bug_refused = "Refused.";
$s_refused_bug_button = "Refused.";
$s_refused_bug_title = "Refused.";
}
?>
regards
Yoann |
|
|
|
| Last updated: Mon, 12 May 2008 - 2:57:38 |
|
|
