Visa denna sidaEditera denna sidaLås denna sidaLänkar till denna sidaBilagor till denna sidaHistorik för denna sidaSwikins toppSenaste ändringarSök i SwikinHjälpguide


Uploaded Image:gjallar.gif

Welcome to the homepage of Gjallar - an easy to use, but highly customizable and advanced web based issue tracker!

If you are looking for mainly a simple "off the shelf" bug tracker for software development only, you might be better off with some of the other open source packages available like for example Mantis. Gjallar on the other hand might be a good fit when:
We do not claim that other open source (or closed source) products do not support these things - but this lists some of the strong areas of Gjallar. And oh, right, you might wonder what Gjallar means. See the longer feature list for more selling points and screenshots for some pictures and explaining text showing off some of the system.

If you want to help us develop Gjallar, read the Guide for developers!


2009-03-05: An unplanned but quite nice release: Gefjon release 0.5!
2009-01-23: A new wiki page describing the new GemStone port and its current status.
2008-11-18: And finally we have the Gangleri release 0.4 out! Hurray! :)
2008-10-13: We just started a more intense development phase using a Compressed Scrum approach, hopefully this leads to the planned Gangleri release 0.4 in a few weeks!
2008-05-23: Oops! A year since the last news item. We have not died or anything, and things have actually been progressing - although slightly slower than earlier. Now we have a new mailinglist of our own!
2007-06-13: Yet another report from the Beach 2007 project.
2007-05-22: A report from the Beach 2007 project.
2007-05-11: The Gjallar project now eats its own dog food and uses Gjallar for Gjallar issues!
2007-05-08: The Beach 2007 project to get Gjallar into a good, working release is initiated!
2007-05-04: Mercurial repository created with a new file tree for Gjallar.
2007-02-14: The breakfast seminar March 15th will be followed by a developer meeting at at Toolkit's office. Anyone interested in Gjallar is invited to both events!
2006-12-18: An alpha-version of Gjallar for Linux has been prepared by Balázs and Levente!
2006-11-22: New release "Andrimner"! See below.
2006-10-27: There is a movie posted as a torrent that includes a Gjallar demo done at the OOPSLA Squeak BOF (and another movie from the BOF).


Gjallar is written in Squeak (Smalltalk) using Seaside (including Scriptaculous) and Magma. It also uses a few external components like Graphviz for autogeneration of state graphs, Swish-e for free text indexing and search, Nullsoft Installer to build a win32 installer and some smaller utilities like unzip and wget. Gjallar has no external dependencies like Apache or IIS and can easily be installed and run out of the box on a laptop for offline usage.


Currently we mainly have "builds" aimed at Squeak developers - not yet a polished enduser release. The three major repositories are:
A Gjallar release number is of the form major.minor.revision where the two first reflect the maturity and amount of change and the revision identifies the Monticello sequence number for the main source code package (called "Q2" for historic reasons).


The Gjallar license is the "new" BSD-license as described at OSI. All contributions to the base project must also be under this license.
The license text is also included in the actual source in the class comment of the class Q2Gjallar.





Gjallar was originally developed by two developers (Göran Krampe and Magnus Kling) at Micronic for inhouse use. Micronic needed a new dynamic issue tracker supporting highly isolated and customized issue processes in combination with offline operation. The available products on the market were either too complex to use or lacked important features, and almost none of the products supported offline operation.

After being developed inhouse for 7 months it was released as an open source project in august 2006. At that point in time the codebase was around 250 classes with 2500 methods totalling about 22600 lines of code (this includes comments, empty lines, filout boiler plate - so in reality it is smaller).


The following links were collected from Google.