Tracker Features

Here's a detailed (but not complete) list of features:

General

Very simple schema. Actions have a title and a due date and are assigned to a single Working Group member. Issues have a title, a description and are related to a product. Issues can only have two states (OPEN and CLOSED).
REST-like interfaces

Simple HTML interface (works on mobile devices)
Summary page of open issues and overdue actions. Also gives details for each user (a slacker tracker).
Issues raised using a Web form
XML output available
Automatically creates links for URIs and Tracker resources (such as other issues and actions)
Meeting preparation summary including: pending review action items, overdue action items, issues recently discussed, etc
Dates can be entered in human readable form (eg “2 weeks” or “next Friday”)
Displays updates made via the Tracker tool (which user made what change)
iCalendar subscription available for each user's due actions.
Coming Soon! RSS feeds for open issues and actions.

Creates actions on the spot so they are automatically linked to the meeting at which they were assigned
Knows the Working Group members so ensures data integrity
Is able to close or reopen actions and issues
Is able to link related issues and actions

All email to the Group mailing list is examined and automatically linked to the relevant issue and/or action.
All new issues sent to the Group mailing list so that the discussion thread can be tracked
Coming Soon! Email reminders of overdue actions.

Other than the features marked Coming Soon above, the follow features are planned for the near future:

Automatic disposition of comments - Mark an issue as Last Call and it will be included in a Last Call DOC for Director review
Public interfaces - Mark an issue as public and allow the public to follow its progress
Clearer identification of related emails (by name and affiliation rather than email address)
Add access keys to Web interface

Got an idea for Tracker? Send the Systeam w3t-sys@w3.org an email. But remember, new features are prioritised by usefulness.