Issues people can name
Readable keys like WEB-42, Markdown descriptions, sub-tasks, links and per-project custom fields.
Optimistic locking · append-only history
The classic JTrac model of projects, workflows and custom fields, rebuilt with a fast interface and rules the server actually enforces.
Features
Workflows, custom fields and KEY-42 issues from the classic tracker, rebuilt with a fast interface and rules the server actually enforces.
Readable keys like WEB-42, Markdown descriptions, sub-tasks, links and per-project custom fields.
Optimistic locking · append-only history
Design statuses and transitions in a visual editor, decide which roles may use each one, and set field rules per status.
Enforced on the server
Boards, filtered lists and timelines, saved views and global search across issues, projects and people.
Dashboards computed per viewer
Comments with @mentions, attachments and notifications, plus a REST API with personal tokens and signed webhooks.
OpenAPI 3 · HMAC-SHA256 · CSV
Then and now
The original JTrac site listed what made it worth installing. Here is each of those features in Jtrac 3, including the ones that work differently or are not there yet.
Available13Changed3Not yet2
| Classic JTrac | Jtrac 3 | How it works now |
|---|---|---|
| Extremely easy to install | Available | One package per OS with Java and PostgreSQL bundled, plus a guided setup wizard. |
| Unlimited project spaces | Available | Organizations, each with its own projects and project keys, like WEB-42. |
| Custom fields and drop-downs per project | Available | Text, number, date, select, multi-select, user and more, with validation. |
| Customizable workflow per project | Available | A visual workflow editor with versioned workflows and role-based transitions. |
| Field-level permissions | Available | Hidden, read-only, optional or required per status and role, enforced by the server. |
| Detailed history view | Available | Attributed, append-only history of every change. |
| E-mail notifications | Available | In-app and e-mail, re-checked per recipient for permissions and field visibility. |
| File attachments | Available | Streamed to disk with SHA-256 and served only after an authorization check. |
| Full text search | Available | PostgreSQL full-text search across issues, plus global search for projects and people. |
| Filter searches by custom fields | Available | Search conditions on custom fields, and saved views shared with the team. |
| Dashboard of statistics | Available | Dashboards with breakdowns, counts, trends and milestone progress, computed per viewer. |
| Export to Excel | Changed | CSV import and export of issues, which spreadsheets open directly. |
| Cross-reference items (duplicate of, depends on) | Available | Links: relates, duplicates and blocks, with dependencies drawn on the timeline. |
| Embedded database and web server | Available | A managed PostgreSQL 18 and the server run from the package; no separate install. |
| Anonymous browsing of projects | Changed | Invited guest members instead of anonymous visitors; project content requires signing in. |
| Various databases supported | Changed | PostgreSQL only, by design; Windows, Linux and macOS packages. |
| Translated into multiple languages | Not yet | English today; more languages are on the roadmap and the layout is RTL-ready. |
| LDAP, Active Directory or CAS sign-in | Not yet | Built-in accounts with Argon2id passwords; no directory or SSO integration yet. |
Classic list as published by the original project. Status checked against this repository; see the README feature reference (opens on GitHub in a new tab).
01Boards, lists, timelines
Drag issues across a board, with keyboard alternatives for every move. Switch to a filtered, sortable list or a timeline with milestones and “blocks” dependencies, and save the view for yourself or your team.
To Do
2In Progress
2In Review
102Workflows and field rules
Each status offers only the transitions its workflow allows, and some are limited to roles: in the Structured template only Administrators can Approve. Field rules make a field hidden, read-only, optional or required per status, here the assignee in review, and the server checks them on every read and write.
03Planning
The timeline lays out scheduled issues against milestones and draws “blocks” dependencies, flagging work that is scheduled to start before its blocker ends. Dashboards then summarize progress, computed for each viewer so nobody sees what they cannot open.
Start with the source, explore available releases, and see how Jtrac fits your workflow.