Backlog vs JTrac

Backlog combines project management, issue tracking, and team collaboration without per-user pricing. Teams can manage issues on Kanban-style boards and use subtasks, Gantt charts, burndown charts, and issue templates, with tools varying by plan. Built-in Git repositories and Subversion support provide code management. Backlog works in a browser and on Android and iOS devices, and its open API supports custom integrations. Listed integrations include Cacoo, Slack, Jenkins, Microsoft Teams, Google Drive, Dropbox, and iCal Sync. The Free plan supports 10 users and one project; it includes 100 MB of storage, Git and Subversion, and a board. Starter costs $35 a month for up to 30 users and five projects. Standard costs $100 a month, and Premium costs $175 a month. Paid plans have a 30-day trial without a credit card, but plans cannot be changed during the trial. Enterprise adds security features such as SAML single sign-on, SCIM provisioning, audit logs, and centralized access management, and can be installed on a private server. Backlog's maker is headquartered in Fukuoka, Japan, and was founded in 2004.

JTrac is a free, open-source issue-tracking web application written in Java and licensed under Apache Software License 2.0. It tracks bugs, action items, and tasks using project-specific fields and workflows. Administrators can set project roles, workflow states, and field-level permissions. Each project space supports up to 10 dropdown fields, 5 free-text fields, 3 numeric fields, and 3 date/time fields. Work tools include item history, file attachments, full-text search, custom-field filtering, dashboards, and Excel export. Status changes trigger email notifications by default, with SMTP configured by an administrator. Authentication options include LDAP, Active Directory, and CAS single sign-on; LDAP handles authentication only, so administrators must also create users and assign them to project spaces. JTrac requires Java 8 or higher, and a JRE is sufficient. It can use its embedded web server and database or be deployed as a WAR in a servlet 3.1 compliant container. The project lists developers, end users, IT, and quality engineers as its intended audience.