manGna! Administration - In Depth Guide

 
 
Show feedback again

Chapter 4. Issue tracker configuration

Savane potentially offers four different issue trackers. They are highly customizable by project admins (as we'll see later), in what concerns both fields and values, and posting permissions. Their purpose and use will therefore largely depend on each project's configuration.

Kinds of trackers

Although they share the same working mechanisms and functionalities, they were created and predefined for different and distinct purposes, inheriting according default values. In Savane's server administration area, we are informed of the purpose and use these trackers are supposed to have:

  1. Support request manager

    Projects are supposed to use it as primary interface with end user.

  2. Bug tracker

    Unlike the support tracker, it is supposed to be used mainly to organize the workflow amongst project members related to bugs. Projects with large audience should probably not accept item posting by people that are not member of the project on this tracker, and instead redirect end user to the support tracker (and only real bugs would be reassigned to this tracker). But that's only a suggestion.

  3. Task tracker

    Unlike the support tracker, it is supposed to be used mainly to organize the workflow amongst project members related to planned tasks. It's the counterpart of the bug tracker for regular and planned activities.

  4. Patch manager

    This is a deprecated issue tracker. As a result, your project might not have the choice to use it. However, it might evolve in the future to a "nameless" issue tracker, leaving up to server or project admins the definition of its purpose.

Through such a tracker scheme, therefore, communication tools (and filters) are provided to direct information from end-users to project managers: end users-->SUPPORT TRACKER-->team members-->BUG TRACKER-->project management-->TASK MANAGER.

Back to the top


Powered by Savane 3.1-cleanup