Byzantine Askemos Language Layer

HoistAbout :: pdf :: context view

inbound links:


Hoist is a very simple issue tracker.

The name stems from HOrrible Simple Issue Tracker -- this would be hosit, which I found as a typo on the net. The metaphor of a tool to attach strings to things and pull them around is a nice one.

Why Yet Another Issue Tracker

There are already enough. I thought so too, however I've been involved several times in the process of selecting a particular one. None ever pleased me. I take this as a sign, there there is no one-size-fits-all wrt. issue tracking. (One of the reasons there where never such a thing for the Askemos project so far.) So custom made trackers according to the desired workflow are often better. The case of Askemos/BALL is even more special: we'd like to attach objects in from the network.

There one more reason to choose hoist even if you don't run an Askemos network yet: If you ticket tracking is a valuable asset to your enterprise and malicious insiders could pose a threat to this data (by way of modification/fraud that is; not only mere disclosure). Using "normal" databases you have no choice; you must eventually trust in your administrator and her/his ability to protect your data. With hoist you don't.

Two historical reasons got this started by now: a) most of the time I avoided heavy exposure to SQL, this had to change one day (so beware, the SQL parts could probably be improved) b) some praxis test of ball's SQL feature, -which recently became stable- where in order.


Workflow / Data Model


Projects are long living objectives. There are per-project to switches to allow a) anonymous reports b) anonymous browsing


Milestones pertain to projects. Milestones mark conditions which are used to measure the progress of the project.

Milestones may have a deadline and a weight and dimension of their gains (currencies etc.).


Issues are items of work reported wrt. projects. They have several states (submitted, accepted, verified, shelling, doomed, solved + seen, recall, reject and spam; whereby the latter increasingly delayed) Issues may be assigned block to milestones until solved.

Issue may have a weight and dimension (e.g., days, man-days, currencies) of their cost.


Comments amend issues. They are intented to be short and displayed as abstracts. Longer comments go into attachments.


Attachments are objects or links augmenting comments.

Those attachments may be anything from binary data, WebDAV directories, Wikis, test cases or any other application.

State Of Development

The project was started mid January 2011.

It does about what is was supposed to initially, but lacks all bells and whistles. It has not even a menu yet.

Last modification: Tue, 25 Jan 2011 18:23:15 +0100

Author(s): jfw,

Document number A26b5619be8d5e3348cca356acfc8efea delivered to public at Tue, 14 Jul 2020 07:47:04 +0200

short comments