Overview

In this tutorial, we will learn about MantisBT Issue Lifecycle. and different MantisBT Issue states.

 

MantisBT Issue Lifecycle

Issue workflow is the process of how the issue is handled in the organization.  The issue workflow consists of transition and issue states/status. The transitions and the order of steps depend on the circumstances of the issue and the issue workflow’s settings.

Every issue has to go through the Issue workflow. The issue attains many states and passes through the workflow during their lifecycle.

New

An issue starts its life when a user( in most cases a Tester) reports and submits an issue to the MantisBT tool. There are several ways to create an issue in MantisBT.

 

Acknowledged

Teams collaborate and decide on valid issues in bug triage sessions. The development team acknowledges or agrees to the issue with the reporter. At this point, the development didn’t yet attempt to reproduce the issue to confirm or assign it to the concerned developer.

Confirmed

The development team moves the issue to the confirmed state suggesting that the issue is reproducible.

Assigned

The issue moves to the Assigned state when it is assigned to a developer for the fix.

Resolved

The issue moves to resolved state when the developer works on the fix. However, there are many resolutions for the issue in MantisBT.

Closed

This issue status reflects that the issue is closed in the system.

—

MantisBT Tutorial

https://www.testingdocs.com/mantis-bug-tracker-tutorial/

Mantis Official Website

https://www.mantisbt.org/