Free issue tracking system software for mac

Issue-Tracker is a support issue tracking system written in PHP, with option of either a PostgreSQL of MySQL backend. The system is designed to be user friendly, and uses a simple modular API to make addition of new modules or features very easy.

Issue-Tracker also includes many features that will allow customer/technical support organizations to take care of customer issues quickly and easy. Some of these features include things like email parsing, email and sms notifications, file uploads, unlimited users and groups, and much more.

Main features:>
- Modular API
- MySQL and PostgreSQL support (MySQL only available in 4.0 and later)
- Unlimited groups
- Group and System Announcements
- Email Interface for pure email interact
- Theme system for easy interface customization
- File uploads
- Support for unauthenticated modules
- Report system for groups and individual users
- Statuses, Categories, and Products editable on per-group basis
- Definable permission set to create roles for users
- Template based for easy UI modifications (Smarty Template Engine)
- Group quotas, either issues or hours based
- Email and SMS alerts

System requirements:
-

Enhancements:
- This release fixes many of the bugs found in 4.0.3 and it is recommended that anyone using 4.0.3 upgrade to this release. For those running releases older than 4.0.3 you will still need to convert your database to the 4.0.3 format before upgrading to 4.0.4.

K4 Publishing System 5.9 is regarded as an easy to use, high performance editorial system for Adobe InDesign CS or CS2 and Adobe InCopy CS or CS2, designed to organise the work of graphic designers and editors, as well as to control the production process.

With its multilevel security controls and robust customization options, K4 supports a transparent and secure production workflow for individual workgroups or entire publishing enterprises across multiple locations.

K4 offers simultaneous workflow between layout and editorial, copy editing at the page stage, content and layout change alerting, workflow routing, status tracking, version control, galley or WYSIWYG editing mode, red lining, change tracking, inline notes and much more.
K4 manages layouts, articles, images, ads, audio/video each with their own fully customizable status workflow. In addition, Microsoft Word manuscripts, Excel spreadsheets, or any other type of file can be managed within the system, centralizing publishing content and making the system available to all participants in the process. Thus, K4 offers unprecedented flexibility for a broad range of professional publishing environments.

One of the hallmarks of K4 is its open SQL interface, enabling other systems such as asset management or automated prepress to be linked to K4. The database will run on all major platforms (Mac OS X, Windows 2000-2004/NT/XP, Linux with Intel hardware, IBM RISC Systeme, Sun Solaris). The administration of K4 is easy and based on a Browser.
Articles are stored in XML format and can be easily repurposed for use on the Web. K4 has been successfully implemented at sites ranging in size from 10 to more than 1,000 users.

The script "iPod tracks ? Desktop" is installed in iTunes script menu.
This script will copy the selected tracks in iTunes (not Playlists) off your iPod onto your Desktop, easily.
If a file with the same name already exists in the destination then the user will be prompted.
The way I found to get tracks copied is my small hack, due to this the script has been saved run-only. Sorry.
The script "iPod tracks ? Choose..." is installed in iTunes script menu.
This script will perform the same action than the previous, but will let you choose in which folder you want to copy the tracks selected in iTunes.
The script "iPod tracks ? encode" is installed in iTunes script menu.
This script will convert the iPod selected track(s) according to the current iTunes conversion preferences, adding them to iTunes main library.
The script "iPod tracks ? iTunes Library" is installed in iTunes script menu.
This script will add the iPod selected track(s) in iTunes main library, and to a library named according to iPods name. If iTunes preferences are set to copy files as they are added to the library, then files will be phisically copied in iTunes Music folder.
The script "iPod tracks (Prefs)" is installed in iTunes script menu.
This script will set up some preferences for the scripts listed above.
The script "Whole iPod Library ? Desktop" is installed in iTunes script menu.
This script will copy the entire iPod library to the desktop, regardless of its internal organization in subfolders. The copy could take a long time, in any case thee user can stop it with the usual Command-. keystroke.
Enhancements
- Faster
- The hack that finds out iPod tracks has been improved
- All file types are now copied, including Apple Loseless, WAV and possibly movies
- Fixed an issue preventing the script to work in some (rare) cases depending on iPod name
- New preferences (standard binary plist)
- Mac-Intel compatibility has been improved
- New names for the scripts, that include extension
- New installer.
System requirements:
- iPod Software 1.3
- iTunes 3 or later.

oops-easytrack is a Bug Tracking System, implemented as a lan-based and a web-based version. Bugs are created, modified, logged or searched.
Users, projects,components and releases can also be administrated. Reports of 4 types may be generated.

Enhancements
- A user with an existing alias or user name could be entered.
- Alias-name and user-name must be unique.
- A project with an existing project name could be added.
- The project name must be unique.
- A release could be added to a project with an existing release name.
- (release name, project) must be unique.
- A component could be added to a project with an existing name.
- (componen name, project) must be unique.
- Maximum Length of names was set to 15 characters.
- In V3.2 the maximum length of names in the tables user, project, release
- and component could be 255 characters.
- This was changed to 15, because these names became now unique keys.
- Saving a user or a bug is now transaction-safe.
- Saving a user or a bug consists of storing 2 records.
- In V3.2 this operation was not transaction-safe.
- In V3.3 it is.
- Viewing documentation in a resizable window.
- When viewing the documentation the window can now be resized.
- View documenation in a browser.
- The documentation is viewed in a JEditorPane with restricted support of
- html. When the client supports browsing for Java applications, then
- the doucumentation can be viewed in a browser.
- No user messages in case of sql errors.
- In V3.2 Sql exceptions were caught and logged, but the user was not informed.
- In V3.3 the user interface catches all sql exceptions and informs the user.
- oops-easytrack aborted, when OOPS_HOME was not set (lan-version only)
- The lan-based version requires, that the environment variable OOPS_HOME was set
- to the installation directory of oops-easytrack.
- If not set, oops-easytrack was stopped.
- In V3.3 if OOPS_HOME was not set but the actual directory contains the
- file ./conf/oops.properties, the user is asked, if he will continue with
- this directory as the home directory of oops-easytrack.
- Editing bug filter: qualified names of components and releases.
- The bug filter editor shows all components and releases, which might
- become confusing, if there are various components or releases with
- the same name but different projects.
- In v3.3 components and releases are qualified by their project name.
- SQL error when database name not equal oops.
- If the name of the database of oops-easytrack differs from oops, then
- a sql error occurred, when logging in.
- In a sql statement the table release must be qualified as dbname.release, because
- release is a reserved key word of MySql. In V3.2 the dbname was hard wired to oops.
- In V3.3 the actual catalog name is used.