View Issue Details

IDProjectCategoryView StatusLast Update
0004466mantisbtadministrationpublic2004-11-06 06:55
Reporterwhereisglenn Assigned Tothraxisp  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Versiongit trunk 
Summary0004466: Problem with custom strings and workflows
Description

I have added a new string to $s_status_enum_string
define( 'TESTING', 70 );

The custom string works in all facets except the value is not recognised when updating a bugs status if you have workflows enabled. eg, b>@@</b is displayed in the, bug_update_page.php and bug_update_advanced_page.php

I have created the custom workflow as follows,
$g_status_enum_workflow[TESTING] ='50:assigned,70:testing,80:resolved,90:closed';

Do I need to add any values to custom_constants_inc.php or custom_strings_inc.php to get this working or is this a bug?

I did try adding the following to custom_strings_inc.php with no success,
$s_status_enum_workflow[TESTING] ='50:assigned,70:testing,80:resolved,90:closed';

TagsNo tags attached.

Relationships

related to 0004328 closedthraxisp Unable to Properly modify Severity List. 
child of 0004350 closeddhx FAQ 
child of 0004297 closedvboctor Mantis 0.19.1 release 

Activities

bpfennig

bpfennig

2004-09-02 09:30

reporter   ~0007396

This is my configuration!

custom_constant_inc.php:


<?
define ( 'to be tested', 60 );
?>

custom_strings_inc.php:


<?
if ( $g_active_language == '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';
?>

config_inc.php:


$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';

$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:confirmed,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[60] ='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';

whereisglenn

whereisglenn

2004-09-02 09:40

reporter   ~0007397

Excellent!

Changed $g_status_enum_workflow[TESTING] to $g_status_enum_workflow[70] and all is working well. Cheers.

sgrund

sgrund

2004-09-02 10:18

reporter   ~0007398

You need also the strings
$s_tested_bug_button
$s_tested_bug_title
$s_email_notification_title_for_status_bug_tested

Wanderer

Wanderer

2004-09-02 12:55

developer   ~0007399

Please, read comments on 0004328

Wanderer

Wanderer

2004-09-02 13:10

developer   ~0007401

Last edited: 2004-09-02 13:13

In common (again)

  1. you have to add own status in custom_constant_inc
    define( 'TESTING', 70 );
  2. you have to add into custom_strings_inc.php for every used language construction
    if (lang_get_current() == <language here>
    {
    $s_status_enum_string = '...,70:testing,...';
    }
    (you have to write all used statuses here)
  3. Because your users will change issue status to this new status "Testing" your custom_strings_inc in each language section also must have two additional strings like (variable name - must have identical, value - can change as you want)...
    $s_testing_bug_button = 'Testing';
    $s_testing_bug_title = 'Test';

After all it will be work as it requested and wanted

edited on: 09-02-04 13:13

jlatour

jlatour

2004-09-02 14:53

reporter   ~0007408

So is this all clear/settled now?

sgrund

sgrund

2004-09-03 01:12

reporter   ~0007419

OK.
But a minor 'bug' still exists (as reported from whereisglenn):

You have to use $g_status_enum_workflow[70]
instead of $g_status_enum_workflow[TESTING]
which would be better.

jlatour

jlatour

2004-09-03 01:23

reporter   ~0007420

Oh, right.

Wanderer

Wanderer

2004-09-03 07:23

developer   ~0007428

Sorry, no!
Have I post here my config?

Wanderer

Wanderer

2004-09-03 07:31

developer   ~0007429

$g_status_enum_string = '10:new,15:reviewed,20:feedback,25:in work,40:confirmed,30:acknowledged,50:assigned,70:verify wait,60:verify fail,80:resolved,90:closed';
...
$g_status_enumworkflow[NEW]='10:new, 15:reviewed, 20:feedback, 25:in work, 40:confirmed, 30:acknowledged, 50:assigned, 70:verify wait';
$g_status_enum_workflow[REVIEWED]='15:reviewed,20:feedback,25:in work,40:confirmed,30:acknowledged,50:assigned,70:verify wait';
$g_status_enum_workflow[FEEDBACK] = '20:feedback,25:in work,40:confirmed,30:acknowledged,50:assigned,70:verify wait';
$g_status_enum_workflow[INWORK]='20:feedback,25:in work,40:confirmed,30:acknowledged,50:assigned,70:verify wait';
$g_status_enum_workflow[CONFIRMED] ='20:feedback,25:in work,40:confirmed,30:acknowledged,50:assigned,70:verify wait'; $g_status_enum_workflow[ACKNOWLEDGED] ='20:feedback,40:confirmed,30:acknowledged,50:assigned,80:resolved';
$g_status_enum_workflow[ASSIGNED] ='50:assigned,70:verify wait';
$g_status_enum_workflow[VERIFY_WAIT] ='60:verify fail,70:verify wait,80:resolved';
$g_status_enum_workflow[VERIFY_FAIL] ='60:verify fail,70:verify wait';
$g_status_enum_workflow[RESOLVED] ='60:verify fail,80:resolved,90:closed';
$g_status_enum_workflow[CLOSED] ='60:verify fail,90:closed';

define( 'REVIEWED', 15 );
define( 'INWORK', 25 );
define( 'VERIFY_FAIL', 60 );
define( 'VERIFY_WAIT', 70 );

if ( $g_active_language === 'english' )
{
$s_fixed_in_version = 'Fixed in version';
$s_severity_enum_string = '10:feature,20:trivial,30:text,40:tweak,50:minor,55:usability,60:major,70:crash,80:block';
$s_status_enum_string = '10:new,15:reviewed,20:feedback,25:in work,40:confirmed,30:acknowledged,50:assigned,60:verify fail,70:verify wait,80:resolved,90:closed';
$s_email_notification_title_for_status_bug_reviewed = 'The following issue has been REVIEWED';
$s_email_notification_title_for_status_bug_in_work = 'The following issue is now RESEARCHED';
$s_email_notification_title_for_status_bug_verify_wait = 'The following issue wait FIX VERIFICATON';
$s_email_notification_title_for_status_bug_verify_fail = 'The following issue has FIX VERIFICATON FAILED';

Last addon for change status

$s_reviewed_bug_button = 'Review';
$s_reviewed_bug_title = 'Review issue';
$s_in_work_bug_button = 'In work';
$s_in_work_bug_title = 'Take issue in work';
$s_verify_wait_bug_button = 'Query';
$s_verify_wait_bug_title = 'Fix verification request';
$s_verify_fail_bug_button = 'Reopen';
$s_verify_fail_bug_title = 'Reopen Issue';
}

jlatour

jlatour

2004-09-04 03:40

reporter   ~0007435

whereisglenn: Where did you put the define line?
bpfenning: I can imagine that a constant with spaces in it doesn't work quite as well.

thraxisp

thraxisp

2004-09-04 07:41

reporter   ~0007438

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.

thraxisp

thraxisp

2004-09-14 18:22

reporter   ~0007582

This information has been added to the manual source.