Search Results for "issue tracking system java"

JTrac is a generic issue-tracking web-application that can be easily customized by adding custom fields and drop-downs. Features include a customizable workflow, field level permissions, e-mail integration, file attachments, a detailed history view and changeable colors to fit a particular CI/CD. After a long hiatus, development has resumed with version 2.2.0 in December 2021, 2.2.1 in February 2022, 2.3.0 in February 2023, 2.3.1 in May 2023, 2.3.2 in July 2023 and 2.3.3 in June 2024. See...

itracker is a true open source issue tracking system. itracker is built using Java enterprise technology. itracker is a professional, easy to use, open, easy to integrate, fast, modular, customizable and scalable solution for all kinds of projects.

WebIssues is an open source, multi-platform system for issue tracking and team collaboration. It can be used to store, share and track issues with various attributes, description, comments and file attachments. The system is easy to install and use but has many capabilities and is highly customizable. Website: https://webissues.mimec.org/ The current development version of WebIssues can be found at https://github.com/mimecorg/webissues

Beet adds user behavior and performance tracking to a Spring-based Java app. HTTP requests, method calls, and SQL statements are tracked and associated to user and session. includes XML, binary XML, and JDBC loggers. See http://beet.sourceforge.net.

Changeset is a web-based issue tracking and configuration management tool. It helps software development teams to manage an efective change requests process. It's developed usign J2EE technology.

Information system to manage execution of manual test scripts. Includes comprehensive issue tracking linked to scripts. Web-based UI, JBoss app server. Standard role-based user access. Test cases written in Excel and loaded up to application using a tool

Dephecto is a web-accessible issue tracking system implemented in Ruby on Rails. Primarily it will be a web service for which a front-end can be written. That is, Dephecto itself will not have an interface other than a RESTful web service API.