Mantis – Issue Lifecycle


Mantis – Issue Lifecycle


”;


Lifecycle denotes different stages or status of issues. Lifecycle starts from reporting an issue and ends when the issue is resolved or closed. An issue mainly can have 3 stages − Open, Resolve, and Close. However, Mantis supports more status as is explained further.

Statuses

New − This is the first status for a new issue when the users report it. The next status may be “feedback”, “acknowledged”, “confirmed”, “assigned” or “resolved”.

Feedback − This status is used for reviewing purpose. Before assigning to a team member, a review process happens to decide the validity of issue and concern team. The next status may be “new”, “assigned”, or “resolved”.

Acknowledged − This status is used by the development team to send a confirmation about receiving an issue or to agree with the reporter’s concern. However, it is possible that they have not yet reproduced the issue. The next status is “assigned” or “confirmed”.

Confirmed − This status is typically used by the development team to reflect that they have confirmed and reproduced the issue. The next status is “assigned”.

Assigned − This status is used to reflect that the issue has been assigned to one of the team members and the team member is responsible to fix it and actively working on it. The next status is “resolved”.

Resolved − This status is used to reflect that the issue has been fixed or resolved. An issue can be resolved among any of the following resolutions. For example, an issue can be called as resolved for “fixed”, “duplicate”, “won’t fix”, “no change required”, or other reasons. The next status is “closed”, or in case if the issue is being re-opened, then it would be “feedback”.

Closed − This status reflects that the issue is closed and successfully validated. No further actions are required on it. Once the issue gets closed, it hides the issue from the View Issues page.

Advertisements

”;

Leave a Reply

Your email address will not be published. Required fields are marked *