Free ticket software for linux

EZ-Ticket provides a multi-user, Web-based ticket/issue tracking system.
EZ-Ticket is a Web-based ticket tracking system, built with simplicity in mind. Unlike other ticket systems, this ticket system has the same functionality that other ticket systems have, without all the complexity, making its use efficient and effective.
INSTALL:
-Unpack the tar file in your document root
-Make sure php is enabled
-use a web browser to hit doc root of the ezt-#.#.# dir. This will start the installer
-follow the installer instructions
-remove the install/ directory
Enhancements:
- cleaned up skin includes
- finished installer
- created basic readme
- cut initial release 0.01
- Implimented e-paging system
- got exporing to work (CSV)
- sticky/announce tickets working
- ticket escalations implimented
- Ported to arrays for selection queries, this allows multiple owners, priorities, etc to be selected
- Implimented "next page" links
- MANY other things
- cleaned up profile.php and added hooks for adding users
- added checks so regular users cant reopen tickets (only admins)
- added sticky ticket support (old PTR announce feature, but a little different)

Ticket linker software contains a set of various plugins for integration of Cerberus Helpdesk system with other systems. A DokuWiki plugin is currently avaiable.

PHP TroubleTicket project is multiuser problem-tracking software entirely written in PHP 4.

It is designed to be used in a web-based client-server environment using the Apache webserver. A client can use just about any modern webbrowser and just about any operating system that is suitable for accessing WWW-Servers like any flavour of Microsoft Windows running the Internet Explorer, Netscape 6 and 7, Mozilla or Opera, Mac OS X or Unix/Linux/BSD systems with Netscape, Opera, Mozilla, KDE Konqueror, Gnome Galeon or Safari.

The dynamic webpages generated by PHP Trouble Ticket are designed to be widely compatible with most browsers and offer a concise and straightforward user interface.

The Bluetail Ticket Tracker (BTT) is a system for creating, storing and keeping track of tickets. A ticket describes an issue of some sort.

It can, for example, be a Trouble Report or a ToDo note. It is available for use (and distribution) under the GNU Public License.

The users of BTT are divided in four different user categories: Staff, Friend, Customer and Anonymous. The access to the data stored in BTT can be tailored for the Friend, Customer and Anonymous groups, while the Staff group has full access rights. This (hopefully) allows BTT to be used both for Open Source Projects as well as in more commercial settings.

In an Open Source Project:

* one or several people (Staff) hosts a site which runs the Ticket handling for a certain application
* a number of people (Staff + Friends) collaborates in the development which also include Ticket handling
* anyone else interested (Customer or Anonymous) may want to check the status of the Tickets (e.g Trouble Reports)

In a commercial setting:

* a company (Staff) runs the Ticket tracker as an aid in their product development.
* the company may be spread geographically or may have development partners (Friends)
* the customers can report problems and track the progression (Customer)

A ticket consists of a number of fields, e.g denoting a release name, component name, responsible person, staus, priority, etc. The actual field values is defined by the Staff when the Bluetail Ticket Tracker is setup. The daily operation of BTT includes creation, editing, searching and viewing of tickets.

The users can also activate the mail alert function which will send a mail to the user when, for example, a new ticket as been assigned to the user.

BTT can also store information about customers which can be useful in a support desk scenario. This makes it possible to connect a ticket with a particular customer. It is also helpful in a support desk scenario where the support engineer quickly need to find information about a customer.

BTT can also store more general information. This Knowledge Base consists of a mail store and a information store.

The mail store makes it possible to retrieve mails (from a POP3 account) and store it locally in a BTT directory. Stored mails can then be searched, viewed and turned into tickets.

The information store is divided in two parts, one external (for users/customers) and one internal (for staff/friends). The external area can for example be used for creating a FAQ (Frequently Asked Question), a HOWTO area. The internal knowledge base is intended for the Staff and/or Friends, and may for example store information such as address lists, how to fill in the expenses form, or contain description of the work process, etc.

Currently BTT supports English, French, German, Spanish and Galician. Adding new languages is easy, one language definition file has to be created with a translation of all text that can be displayed. (If you do this, make sure to send the new language file to the maintainers so that it can be incorporated into the standard release).

Tickets can also be retrieved and stored via a Unix command line interface.

WebService::TicketAuth is a ticket-based authentication module for SOAP services.

SYNOPSIS

@WebService::MyService::ISA = qw(WebService::TicketAuth);

WebService::TicketAuth is an authentication system for SOAP-based web services, that provides a signature token (like a cookie) to the client that it can use for further interactions with the server. This means that the user can login and establish their credentials for their session, then use various tools without having to provide a password for each operation. Sessions can be timed out, to mitigate against a ticket being used inappropriately.

This is similar in philosophy to authenticated web sessions where the user logs in and gains a cookie that it can use for further interactions. For example, see Apache::AuthTicket. However, such systems require a web server such as Apache to handle the authentication. This module provides a mechanism that can be used outside of a web server. In particular, it is designed for use with a SOAP daemon architecture.

This module was originally developed by Paul Kulchenko in 2001. See guide.soaplite.com for more info.

FUNCTIONS

new()

Creates a new instance of TicketAuth. Establishes several private member functions for authentication, to calculate, make, and check the authInfo.

get_error()

Returns the most recent error message. If any of this modules routines return undef, this routine can be called to retrieve a message about what happened. If several errors have occurred, this will only return the most recently encountered one.

ticket_duration($username)

This routine defines how long a ticket should last. Override it to customize the ticket lengths. The username is provided when requesting this information, to permit applications to vary ticket length based on the users access level, if desired. If $username is undef, then a generic duration should be returned.

By default, the ticket duration is defined to be 20 minutes (or 20*60 seconds).

get_username($header)

Retrieves the username from the auth section of the SOAP header
is_valid($username, $password)

Routine to determine if the given user credentials are valid. Returns 1 to indicate if the credentials are accepted, or undef if not. Error messages can be retrieved from the get_error() routine.

Override this member function to implement your own authentication system. This base class function always returns false.

login()

This routine is called by users to establish their credentials. It returns an AuthInfo ticket on success, or undef if the login failed for any reason. The error message can be retrieved from get_error().

It checks credentials by calling the is_valid() routine, which should be overridden to hook in your own authentication system.

TrackIt is the first open source, web based project tracking tool designed from the ground up to provide maximum customization, flexibility and most importantly, usefulness to the developer.
Flexibility: Use TrackIt To Meet Your Needs
Aside from the simple definition of a Project and Users, every feature in TrackIt is optional. Furthermore, TrackIts dynamic linking system gives flexibility to define the links that make sense for your projects process. TrackIt also gives two powerful means to view your projects data. The first is a high level Listing capability, driven by HQL, to view common attributes of the projects items. The second is a raw SQL query used for reporting to CSV, a flexible format that imports into many tools such as Excel, Access, and Open Office.
Customization: Define Unlimited Project Item Types
Out of the box TrackIt comes with builtin support for several XP item types such as Features, Trouble Tickets, Test Cases, Derived Requirements, and many more. However, if these dont meet your projects needs, you can edit and add item types on the fly to make TrackIt work how you need it to.
Usefulness: Custom Developer Content
One of the primary goals of TrackIt was to be useful to the developer. Many Project Tracking tools do an adequate job of supporting project items, but come up short in terms of developer appeal. In TrackIt, each user has:
Up to four customizable RSS Feeds
A customizable rich content area useful for a todo list or personal notes
A high level view of all ticket types pertaining to the user
Eclipse Plugins for common activities (Preliminary support in 1.0 RC2)
On this site you will find links to resources and tips that will help your projects get the most out of TrackIt.
Enhancements:
- Better transactionality management, user interface enhancements, updates to dependent libraries, and several small bugfixes.