Welcome to the sysadmin tracker for the Roundup issue tracker system. It requires release 1.6.0 or newer of the Roundup issue tracker. It will not work with any 1.5.x or earlier release of roundup.

This tracker is designed to handle issues generated in a system administration or help desk environment. It is released under the GPL license see the Tracker License section for details.

You can find Download Links on the download page. A demo instance of the tracker is located at: https://rouilj.dynamic-dns.net/demo/.

It is more complex than the classic tracker, but has things that I have wanted in my trackers. Some of the functions were inspired by equivalent functionality in Request Tracker (rt) while some other things I have wanted in various trackers (req, reqng, queuemh, rt, clearquest, remedy, cherwell, jira) through the years. This tracker started out as an experiment to get rt's comment capability added to the classic tracker. I was able to do that in about 4 hours of effort learning Python as I went.

See the current manual in your browser. You can also get a version of the manual in pdf.

The sysadmin tracker builds on the basic functions of the classic Tracker: status, keywords, owner, and nosy list support. A summary of additional features:

• Issue relationships
  • Dependencies - closing all dependencies of an issue open the issue, issue can't be resolved until all its dependencies are resolved.
  • Grouping - arrange issues in a hierarchy that allows batch operation and distributes notifications across the hierarchy
  • See also - generic relationships between issues
• Private mode restricting access to tickets
• Notification/collaboration
  • the previously mentioned two levels of notification/messages (Watchers and Technical users)
  • highlighting tickets in the web interface that need a response (works great with the new auto-refresh mode)
  • Adding a particular topic/keyword to an issue will add users to the Watcher mailing list for that issue.
  • Public and custom RSS feeds
• Scheduling/Workflow
  • support for start date, due date, lead time
  • support for a working order field to provide fine grained prioritization of issues
  • six predefined priorities (with support for adding more)
  • support for queues to email groups automatically when an issue is assigned
  • define valid transitions in ticket status to implement a workflow
• Automatic/scheduled actions so you can auto-close a ticket in three days if there is no response.
• Usability
  • Web interface provides basic responsive design support for use on a tablet or phone
  • Batch-update mode that allows adding an email and setting fields in a form and applying it to multiple issues.
  • Multi-edit mode that allows applying different changes to different issues all from one screen.
  • Replying to an update in the web interface can pre-fill the reply with quoted text of the update
  • Fields for recording billing and reference information (so you can find Sun's ticket number without having to read all of the messages 8-))
  • Combined full text search and jump to issue box
  • Works with text based browsers so basic functionality can be done on remote servers (E.G. uploading a local file or quickly updating a ticket over a serial terminal in a data center.)