Arbit aims to provide a decent modern extensible multi project tracking tool. Features start with issue tracking and wiki and do not stop before code analysis and translation management.
Arbit aims to provide a decent modern extensible multi project tracking tool. Features start with issue tracking and wiki and do not stop before code analysis and translation management.
Arbit consists of several modules, which you can choose to use or not to use for your own bug tracking interface. These are some of the main modules:
A simple issue tracking system, configurable in types of issues, states etc., with basic reporting functionality. The heart of every issue tracker.
A simple ReST based wiki. This is a useful tool for end-user documentation and for documenting the development process.
The source code browser operates on the latest checkout of your project sources. It provides diffs for every file and every commit. Useful for pointing at code snippets in discussions or inside the documentation.
Transformation of all internal arbit signals into mails, which can yet only be sent to the users mail address, but will also be extended to support other messaging protocols. With this module you can define in how much detail you want to be informed about new issues, users or changes in the documentation.
A module to manage and answer user contributed questions. You will probably need this in bigger end-user projects.