View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008889||mantisbt||public||2008-02-14 10:16||2011-06-22 11:53|
|Summary||0008889: Status change notification never sent for multi-word status names|
Status change emails are never sent for status names that contain spaces.
This is due to a bug in bug_core.api. This bug exists in HEAD and all releases.
See additional information for specifics.
|Steps To Reproduce|
Add a custom status that is more than one word e.g. "Awaiting Test".
$t_status is eventually used in a call to email_notify_flags. Problem is here is has its spaces replaced with underscores but the data in the notify_flags array doesn't. Hence the call to email_notify_flags will always fail.
|Tags||No tags attached.|
unfortunately the suggested fix seems to fail in version 1.1.0
using $t_status2 instead of $t2_status in suggested fix works like without using fix (no advantage for the status names containing spaces but the others getting sent)
The design is not to ever have spaces in the status names. For example, if you want to define status "Awaiting Test" with id 60, then you should define it as follows:
In the $g_ enum, you use "60:awaitingtest".
Anywhere in the configuration, you use the "awaiting_test" name, rather than the localized name which has the capitalization and the spaces.
confirmed: I have obeyed this rule, nevertheless I've had the "send mail on status change" box in user's configuration not set. There are several settings above for "send mail on 'confirmed'", "...'reopened'" and so on, so this was why only SOME status changes have been sent by mail (unfortunately those were the ones with spaces in their s_string variable - which is really irrelevant).
Thanks. Following Victor's design rule works as expected without code changes.
It would be useful if the documentation reflected that. The example given in http://www.mantisbt.org/manual/manual.customizing.mantis.customizing.status.values.php
This works for me too! Why not closing this issue, i had to click through all related tickets to find this one. All related bugs in the original were marked as new and related.
|2008-02-14 10:16||a_crossley||New Issue|
|2008-02-16 16:13||pluntke||Note Added: 0017067|
|2008-02-16 16:36||pluntke||Note Added: 0017071|
|2008-02-17 01:07||vboctor||Note Added: 0017086|
|2008-02-17 05:07||pluntke||Note Added: 0017089|
|2008-02-18 09:12||a_crossley||Note Added: 0017096|
|2010-12-27 15:09||atrol||Relationship added||related to 0009406|
|2011-06-22 11:53||ojonatan||Note Added: 0029052|