|
|
As per documentation:
https://mantisbt.org/docs/master/en-US/
There are two config options that relates to your question:
Set status on assignment of handler $g_auto_set_status_to_assigned change status when an issue is assigned
Status to set auto-assigned issues to $g_bug_assigned_status status to use when an issue is auto-assigned
First, notice that when $g_auto_set_status_to_assigned is OFF (default=ON), you can have an issue "assigned to" one person, but still in status "new". So both "assignment" and "status" can be modified independently.
When this option is ON, the action of "assign" an issue to a person, will automatically change its status to "assigned status". This status is the one defined by the option $g_bug_assigned_status.
Two points here:
- $g_bug_assigned_status may be used by other places in code to define what is an "assigned status" (eg: reassign on feedback)
-
This automatic status change is only performed with some conditions. See documentation:
$g_auto_set_status_to_assigned
Automatically set status to $g_bug_assigned_status whenever a bug is assigned to a person. Installations where assigned status is to be used when the defect is in progress, rather than just put in a person's queue should set it to OFF. Default is ON. For the status change to be effective, these conditions must be met:
Bug has no handler, and a new handler is selected
The assignment is not part of a explicit status change
Current bug status is lower than defined "assigned" status
"Assigned" status is reachable by workflow configuration
If the conditions are not met, the assignment is still made, but status will not be modified.
Regarding category auto-assignment:
When a category "owner" is defined, afaik the only operation that is performed is that the issue is immediately assigned to that user.
If $g_auto_set_status_to_assigned is set to ON, the status change is triggered regardless of whether the assignment was manual or automatic.
I can see probably we have a misleading description of
"Status to set auto-assigned issues to $g_bug_assigned_status"
so you may think that this is the status which an issue is set when its assigned automatically to the category owner.
Actually, this is the status to be interpreted as "assigned", in a generic workflow situation. |
