trouble with @50@ @80@ @90@ in workflow

[olivier.schenk@infopro.ch]

Hello

I've got a problem with mantis. I defined a workflow with only 4 statuses.

new_created, in_process, closed, re-opened.

this is what i did:

custom_constant_inc.php
--------------------------------------------------------------------------------
<?php
define ( 'BUG_NEW_CREATED', 10 );
define ( 'BUG_IN_PROCESS', 20 );
define ( 'BUG_CLOSED', 30 );
define ( 'BUG_RE_OPENEND', 40 );
?>
--------------------------------------------------------------------------------

custom_string.php
--------------------------------------------------------------------------------
<?php
if ( lang_get_current() == 'german' ) {
$s_status_enum_string = '10:Neu,20:In Bearbeitung,30:Geschlossen,40:Wieder geoeffnet';

} else {
$s_status_enum_string ='10:new,20:in process,30:closed,40:re-opened';
}
?>
--------------------------------------------------------------------------------

config_inc.php - Only the relevant part
--------------------------------------------------------------------------------
# Status to assign to the bug when submitted.
$g_bug_submit_status = BUG_NEW_CREATED;

# Status to assign to the bug when assigned.
$g_bug_assigned_status = BUG_IN_PROCESS;

# Status to assign to the bug when reopened.
$g_bug_reopen_status = BUG_IN_PROCESS;

# Resolution to assign to the bug when reopened.
$g_bug_reopen_resolution = BUG_CLOSED;

# --- status thresholds (*_status_threshold) ---

# Bug becomes readonly if its status is >= this status. The bug becomes read/write again if re-opened and its
# status becomes less than this threshold.
$g_bug_readonly_status_threshold = BUG_CLOSED;

# Bug is resolved, ready to be closed or reopened. In some custom installations a bug
# maybe considered as resolved when it is moved to a custom (FIXED OR TESTED) status.
$g_bug_resolved_status_threshold = BUG_CLOSED;

# Automatically set status to ASSIGNED whenever a bug is assigned to a person.
# This is useful for installations where assigned status is to be used when
# the bug is in progress, rather than just put in a person's queue.
$g_auto_set_status_to_assigned = OFF;

# 'status_enum_workflow' defines the workflow, and reflects a simple
# 2-dimensional matrix. For each existing status, you define which
# statuses you can go to from that status, e.g. from NEW_ you might list statuses
# '10:new,20:feedback,30:acknowledged' but not higher ones.
$g_status_enum_workflow[BUG_NEW_CREATED]='20:in process,30:closed';
$g_status_enum_workflow[BUG_IN_PROCESS] ='30:closed,40:re-opened';
$g_status_enum_workflow[BUG_CLOSED] ='40:re-opened';
$g_status_enum_workflow[BUG_RE_OPENEND] ='20:in process,30:closed';
$g_status_enum_workflow = array();
--------------------------------------------------------------------------------

Ok when I click now on the Status Field on a new Bug I get the options "in process", "closed" and @50@, @80@, @90@.

My first solution to this problem was to dissable all @... statuses on the manage workflow page but this seems only like a temporary solution.

Does anyone have an idea how to get this @50@, @80@.. out of my workflow?

Thanks alot Olivier

My Configuration: IIS, PHP 5.1 Win2003, Mantis 1.0.6.

[deboutv]

You also need to update $g_status_enum_string in the config_inc.php file.

[olivier.schenk@infopro.ch]

Thanks alot.

I've added this line to config_inc.php
------------------------------------------------------------------------------------

Code: Select all

[i]$g_status_enum_string				= '10:new,20:in process,30:closed,40:re-opened';[/i]

-------------------------------------------------------------------------------------

and it works.

Best wishes Olivier