Mantis Logo
Mantis Manual
Manual
Page Descriptions
System Management Pages
Manage Configuration

Workflow Thresholds
Workflow Transitions
Email Notifications


Partner Links


Workflow Transitions
Last Modified: April 17, 2005 18:04PM
(Introduced in 1.0.0)
Description

This page covers the status workflow. For most of these, the fields are self explanatory and relate to a similarly named setting in the configuration file. At the right of each row is a selector that allows the administrator to lower the access level required to change the particular parameter.

The values changeable on this page are:

Issues

TitleVariableDescription
Status to which a new issue is set$g_bug_submit_statusstatus issue is set to when submitted
Status where an issue is considered resolved$g_bug_resolved_status_thresholdstatus where bug is resolved
Status to which a reopened Issue is set$g_bug_reopen_statusstatus issue is set to when reopened


The matrix that follows has checkmarks where the transitions are allowed from the status on the left edge to the status listed across the top. This corresponds to the $g_enum_workflow array.

At the bottom, there is a list of access levels that are required to change the status to the value listed across the top. This can be used, for instance, to restrict those who can close an issue to a specific level, say a manager. This corresponds to the $g_set_status_threshold array and the $g_report_bug_threshold setting.

User Contributed Notes
Workflow Transitions
Add Notes About Notes
nteeuwen@hotmail.com
13-Dec-2005 10:15
#768
Can anyone tell me how the default statuses are to be used?

New -> feedback -> acknowledged->confirmed->assigned->resolved->closed

New - pretty obvious
Assigned - developer ready to fix the bug
Resolved - developer resolved the bug
Closed - If the developer fixed the bug, a tester has confirmed it and closed the issue. There are other scenarious for this but this would be the primary one.

I am not quite sure where feedback, acknowledged and confirmed fit in.

I would think feedback would be something a developer might set the bug to if they need feed back from the reporter on the issue.
dcw@infonie.fr
13-Dec-2005 11:59
#770
I think that "feedback" is to be used when the developper wants more information (or explanation) about the bug
bart.veldhuizen@nuon.com
11-Jan-2006 8:46
#821
We use 'acknowledged' to confirm that a new issues has been reviewed and that it is indeed a bug and that it contains enough information to be reproduced/analysed. However, at this time we will not start work on it.

Once we start a new release and the issue needs to be addressed (in this release), its status will change to 'confirmed'.

Once an issue gets assigned to a developer, he is expected to work on it ASAP. So we will never have developers that have hundreds of issues assigned to them.

Cheers,

Bart
teo.nomail@noplace
24-May-2006 18:13
#1089
Hi to all
Do you know if it is possible to edit the default name for the WF steps?
I'd like to change them to include some testing phase ... something like:

NEW REQUEST -> DEVELOPING -> MOVE TO TEST ENV -> USER TEST -> MOVE TO PROD -> UPDATE MANAULS.


Thanks in advance
nicolas.ng.gauthier@alcatel.fr
08-Aug-2006 9:23
#1216
==> any update on this ? I also would like to understand if the default WF steps can be:
1) renamed
2) modified

Thanks !


Hi to all
Do you know if it is possible to edit the default name for the WF steps?
I'd like to change them to include some testing phase ... something like:

NEW REQUEST -> DEVELOPING -> MOVE TO TEST ENV -> USER TEST -> MOVE TO PROD -> UPDATE MANAULS.
n/a
18-Aug-2006 0:33
#1240
Dear all,

I am evaluating and also interested to know how the workflow be customized to suit my company needs. Besides, what would be impacts on future upgrade if the workflow has been customized?

Thank you.

Regards,
Francis
Eric B.
25-Oct-2006 10:01
#1277
Customizing is possible for status, roles and workflow. You should read these pages:
http://manual.mantisbugtracker.com/manual.customizing.mantis.php
http://manual.mantisbugtracker.com/manual.customizing.mantis.enumerations.php
http://manual.mantisbugtracker.com/manual.customizing.mantis.customizing.status.values.php
tom
18-Jan-2007 8:11
#1358
Updated links (from the previous comment):
http://manual.mantisbt.org/manual.customizing.mantis.php
http://manual.mantisbt.org/manual.customizing.mantis.enumerations.php
http://manual.mantisbt.org/manual.customizing.mantis.customizing.status.values.php
Add Notes About Notes
Last updated: Fri, 16 May 2008 - 11:23:42

Mantis @ SourceForge