Site Tools


Hotfix release available: 2024-02-06a "Kaos". upgrade now! [55.1] (what's this?)
New release available: 2024-02-06 "Kaos". upgrade now! [55] (what's this?)
Hotfix release available: 2023-04-04a "Jack Jackrum". upgrade now! [54.1] (what's this?)
New release available: 2023-04-04 "Jack Jackrum". upgrade now! [54] (what's this?)
Hotfix release available: 2022-07-31b "Igor". upgrade now! [53.1] (what's this?)
Hotfix release available: 2022-07-31a "Igor". upgrade now! [53] (what's this?)
New release available: 2022-07-31 "Igor". upgrade now! [52.2] (what's this?)
New release candidate 2 available: rc2022-06-26 "Igor". upgrade now! [52.1] (what's this?)
New release candidate available: 2022-06-26 "Igor". upgrade now! [52] (what's this?)
Hotfix release available: 2020-07-29a "Hogfather". upgrade now! [51.4] (what's this?)
internal:pm:mantis

Status in Mantis

  • New - This is the landing status for new issues. Issues stay in this status until they are assigned. The next status can be “assigned” or “resolved”.
  • Assigned - This status is used to reflect that the issue has been assigned to one of the team members. The next status is typically “acknowledged”.
  • Acknowledged - This status is to indicate that the assigned team member is presently working on the ticket, the next status can be “resolved” or “feedback”.
  • Feedback - This status is to indicate that the assigned team member needs information/clarification from the product management team. (This feedback status can be set by the team member only when the product management team does not have a immediate(>1/2 day) solution/feedback to the issue/feature.
  • Resolved - This status is used to reflect that the issue has been resolved. An issue can be resolved with one of many resolutions. For example, an issue can be resolved as “fixed”, “duplicate”, “won't fix”, “no change required”, etc. The next statuses are typically “closed” or in case of the issue being re-opened the status will be assigned.
  • Closed - This status reflects that the issue is completely closed and no further actions are required on it. It also typically hides the issue from the View Issues page. Some teams use “closed” to reflect sign-off by the reporter and others use it to reflect the fact that the fix has been released to customers.

Tickets in Mantis

  • Each Feature which is required will be logged in as a feature ticket in Mantis.
  • The Ticket will be assigned to a member of the Product Management team member
  • The assigned member will create 3 clone tickets to the feature ticket and assigned it to the leads of the respective teams.
    • Clone Ticket 1 - Assigned to Product Management Team member
    • Clone Ticket 2 - Assigned to Development Team
    • Clone Ticket 3 - Assigned to Testing team

Guidelines to Creating Tickets in Mantis

1. Report a new Issue/Feature with the following details

  • Product Version
  • Steps to reproduce in case of an issue
  • Use Case & Business Case in case of a feature requirement

2. Do not assign tickets to any individual resource.

internal/pm/mantis.txt · Last modified: 2022/06/14 10:16 (external edit)