Tracker module: Difference between revisions

From MoodleDocs
Line 43: Line 43:
*Requirers: any user able to post a ticket.
*Requirers: any user able to post a ticket.


Internal tracker roles are bound to Moodle roles through the tracker specific capabilities. See the tracker capabilities documentation beneath for more information.
Internal tracker roles are bound to Moodle roles through tracker specific capabilities. See the tracker capabilities documentation beneath for more information.


==Screens==
==Screens==

Revision as of 13:06, 31 December 2009

Module overview

This module provides a light but full featured ticket tracker within a Moodle environment. This tracker could be used by administrators to collect issues from Moodle end users, or may be as a real bug tracking tool for project oriented activities.

Recently has the semantics of the string being reviewed to allow a more general scope use of the tracker, whenever the need of "service ticketting" appears.

The internal tracker module of Moodle have following features :

Tracker configuration

  • Setting up ticket form elements
  • File attachment fields available

Ticket management

  • Collecting tickets
  • Assigning tickets to assignees
  • Status workflow (posted, opened, working, testing, resolved, blocked, abandonned, transfered).
  • Suscribing to ticket's notifications
  • Notifying changes to suscribers
  • Complete personal management of notifications and subscriptions
  • Summary of capabilities and owned tickets
  • Separating concluded tickets (resolved, abandonned, transferred) from working tickets (posted, working, blocked)
  • Ticket dependancy chaining
  • Messaging threads (globally disablable) attached to tickets

Priority related features

  • Managing ticket priority (controls are active when choosing priority as ordering criteria)
  • Asking for priority raise from the owner of the ticket

Moodle Network functions

  • Moodle Network across cascading from a tracker to a remote tracker (local cascade works either within the same Moodle instance).

Local Roles Management

Tracker has its own internal user profiles, that will merely separate population into:

  • Administrators: will be allowed to change the form structure and all settigns of the tracker instance
  • Resolvers: are allowed to change the ticket status and thus closing or resolving tickets. They also can assign tickets to developers.
  • Developers: usually people that will handle the ticket and search for a solution.
  • Requirers: any user able to post a ticket.

Internal tracker roles are bound to Moodle roles through tracker specific capabilities. See the tracker capabilities documentation beneath for more information.

Screens

Common user screens

  • Bug recollection form
  • Viewing bug list
    • Exploring bug list (non manager mode)
    • Searching a bug
    • Viewing a bug description
  • User profile, stats and shortcuts
    • My preferences : choosing on which events to be notified
    • My watches : managing which bug entries I receive notifications from
    • My searches : managing stored search queries for my own

Resolver screens

  • Viewing bug list
    • Exploring bug list (manager mode)
    • Editing a bug entry

Administrator screens

  • Activity summary
  • Managing bug tracking form elements

Capabilities

Capabilities for Tracker module (1.9)