Mantis Logo
Mantis Manual
Manual
Configuration

Database
Path
Webserver
Version
Email
Language
Display
Time
JpGraph
Date
News
Default Preferences
Summary
Bugnote
File Upload
HTML
Authentication
Status Settings
Filters
Misc
Colors
Cookies
Database Tables
Speed Optimisation
Reminders
Bug History
Sponsorship
Source Control Integration
Custom Fields
My View Settings
Relationships
System Logging


Partner Links


Status Settings
Last Modified: December 12, 2004 09:12AM
(0.18.0)
Description

$g_bug_submit_status Status to assign to the bug when submitted. Default value is NEW_. Added in 0.18.1
$g_bug_assigned_status Status to assign to the bug when assigned. Default value is ASSIGNED. Added in 0.18.1
$g_bug_reopen_status Status to assign to the bug when reopened. Default value is FEEDBACK. Added in 0.18.1
$g_bug_reopen_resolution Resolution to assign to the bug when reopened. Default value is REOPENED. Added in 0.18.1
$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.
$g_bug_resolved_status_threshold 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_readonly_status_threshold
$g_update_readonly_bug_threshold
Bug becomes readonly if its status is >= $g_bug_readonly_status_threshold. The bug becomes read/write again if re-opened and its status becomes less than this threshold. The default is RESOLVED.
Once the bug becomes readonly, a user with an access level greater than or equal to $g_update_readonly_bug_threshold can still edit the bug. Added in 0.19
$g_status_enum_workflow '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.
The default is no workflow, where all states are accessible from any others. Added in 0.19
$g_report_bug_threshold This is the access level required to open a bug. The default is REPORTER.
$g_update_bug_threshold This is the access level generally required to update the content of a bug. The default is UPDATER.
$g_handle_bug_threshold This is the access level generally required to be access level needed to be listed in the assign to field. The default is DEVELOPER.
If a more restrictive setting can be determined from $g_set_status_threshold, it will be used.
$g_update_bug_status_threshold
$g_set_status_threshold
These settings control the access level required to promote a bug to a new status once the bug is opened.
$g_set_status_threshold is an array indexed by the status value that allows a distinct setting for each status. It defaults to blank.
If the appropriate status is not defined above, $g_update_bug_status_threshold is used instead. The default is DEVELOPER. Added in 0.19
$g_allow_close_immediately If set, bugs are allowed to be resolved and closed in one action. The default is OFF.
$g_allow_reporter_close If set, the bug reporter is allowed to close their own bugs, regardless of their access level. The default is OFF.
$g_allow_reporter_reopen If set, the bug reporter is allowed to reopen their own bugs once resolved, regardless of their access level. This allows the reporter to disagree with the resolution. The default is ON.
See also: Customizing Status Values

User Contributed Notes
Status Settings
Add Notes About Notes
There are no user contributed notes for this page.
Last updated: Sun, 14 Mar 2010 - 21:05:12

Mantis @ SourceForge