JTrac

JTrac is a free, open-source issue tracker for teams willing to run a Java application themselves. It fits developers, IT groups, quality engineers, and end users who need different workflows and permissions by project. Choose it for configurable, self-hosted issue management; look elsewhere if you need automation, roadmaps, or time tracking.

Overview

JTrac organizes bugs, action items, and tasks into project spaces. Each space can define its own workflow states, project roles, and field-level permissions, so teams with different processes do not have to share one rigid template. That flexibility is the product’s central advantage, while operating the server remains your responsibility.

Installation requires Java 8 or newer; a JRE is sufficient. For a quick deployment, JTrac includes an embedded Jetty web server and HSQLDB database. Administrators can instead deploy a WAR file in a servlet 3.1-compliant container. The database and uploaded attachments reside in JTrac’s home directory, making regular production backups essential. The installation guidance also calls for changing the default administrator password, particularly when exposing the system to the internet. Development began in 2004, and the project is released under the Apache Software License 2.0.

Key features

Custom fields let each project capture information in dropdown, free-text, numeric, and date/time formats. The per-project ceiling is 10 dropdown fields, 5 free-text fields, 3 numeric fields, and 3 date/time fields. Those limits suit focused issue forms, but they can become restrictive for projects that need extensive structured data.

Every item keeps a history and can include file attachments. Full-text search, custom-field filtering, dashboards, and Excel export help teams find and summarize work without relying on a separate reporting tool. These are practical controls for issue queues, though JTrac does not provide roadmaps, time tracking, or workflow automation.

Status changes send email notifications by default. Administrators configure the SMTP server, including authenticated or SSL connections, so delivery depends on correct mail-server setup. LDAP, Active Directory, and CAS single sign-on are supported. LDAP handles authentication only: administrators must still create JTrac users and map them to project spaces, adding setup work for directory-managed organizations.

Documentation lists translations for 23 locales. The FAQ points users to SourceForge trackers for bug reports and feature requests and welcomes code contributions and translations, which is appropriate for an open-source project but does not replace a managed support desk.

Pricing

There are no subscription seats or hosted quotas in this plan because you run the software yourself. The trade-off for the zero license cost is administrative: your team supplies the Java environment, deployment, backups, authentication setup, email configuration, and ongoing maintenance.

Platforms

JTrac is delivered as a self-hosted web application and runs on Linux, macOS, and Windows environments. Java 8 or higher is required. You can use the bundled server and database or place the WAR deployment in a compatible servlet container, giving administrators options without turning it into a managed cloud service.

Who it's for

JTrac is a strong match for developers, IT departments, quality engineers, and end users who need project-specific fields, workflows, and permissions and have staff comfortable maintaining Java software. It also suits organizations that prefer open-source licensing and control over where issue data and attachments are stored.

It is a weaker choice for teams seeking a hosted experience, built-in workflow automation, roadmap planning, time accounting, or minimal directory administration. Projects with unusually elaborate custom forms should evaluate the per-type field caps before committing.

Pros and cons

Pros

• Project-level control: Independent workflows, roles, and field permissions adapt to different team processes.
• Useful issue analysis: History, attachments, full-text search, dashboards, custom filters, and Excel export cover core tracking and reporting needs.
• Flexible deployment: Embedded Jetty and HSQLDB simplify initial setup, while WAR deployment supports servlet containers.
• No license fee: Apache-licensed open-source software avoids per-user subscription charges.
• Directory options: LDAP, Active Directory, and CAS authentication can connect with existing identity systems.

Cons

• Self-hosting burden: Java runtime management, backups, mail configuration, security hardening, and upgrades remain with your administrators.
• LDAP is not full provisioning: Users still need JTrac accounts and project-space mappings after authentication.
• Bounded custom fields: The 10/5/3/3 limits may not fit data-heavy projects.
• No automation, roadmaps, or time tracking: Teams needing those planning and operational functions will need another system or process.

Alternatives

Issue Tracking Software is the broader category to compare when you want options beyond a self-hosted Java tracker.

Pick Linear instead for a freemium web and desktop/mobile service whose free tier allows unlimited members, two teams, and 250 issues. Choose YouTrack when a hosted option with a free plan for up to 10 users and 30 GB of storage is more suitable.

GitHub Codespaces is a freemium, multi-platform choice with usage-priced compute plans, while Azure Test Plans targets teams that specifically need test planning alongside its paid Basic + Test Plans tier.

Choose Backlog for a hosted freemium service with a 10-user, one-project, 100 MB free tier. Bugzilla, MantisBT, and Trac are other free, self-hosted project options to consider.

Verdict

JTrac is a sensible choice for technically capable teams that want open-source issue tracking, project-specific workflows, and control of their own deployment at no license cost. Its strongest differentiator is fine-grained per-project configuration. Look elsewhere if your priority is a managed service, automated workflows, roadmap and time-planning features, or simpler LDAP onboarding.