Abstract

This week has a short introduction to Mantis, the issue tracking system that will be used for the course projects. Following this brief introduction, course projects will be discussed.

Issue Tracking

• Often used as a bug tracking system for software development
• Issues are anything which needs resolution
  • bugs in an existing implementation
  • requests for a feature which should be added
  • ideas for future features which should be captured
• Issue tracking is not chatting
  • please do not have conversations using the system
  • each issue and each note should have substance to it
• Try to resolve issues to the point where they can be closed

Mantis Structure

• Users get a login and have access to the application
• Each installation can have multiple projects
  • users have access to the projects which are public or open to them
• Each project has a list of issues
  • the category describes which part of a project an issue is for
  • the severity describes how important the issue is
  • the status tracks an issue through its lifecycle (until it is closed)
• Categories identify well-defined parts of a project
  • issues entered for a category are assigned to a default user
  • issue assignment can be changed manually at any time
• Adding notes to an issue can be done in two ways
  • just adding a note without changing its status
  • changing its status and then adding the note which describes the status change
• Issues can be monitored to get emails about activities