Site Network:

Bugs

Attachments working now!

Well, I've successfully added uploading of attachments to tickets. You can even add additional attachments by updating the ticket. In addition to that, if you upload source code, it is viewable and it's syntax is even highlighted.

At the moment only HTML, PHP, CSS, Python, Perl, Ruby, Javascript and Pascal are supported, but I'm busy working on supporting more languages.

I've updated the demo for those who want to play around with it, and I'll release an egg file once I've done a little more testing and bug fixing.

 

Ticketing (Bug Tracking) Underway

The last 2 weeks I've managed to get some time to work on Project HQ, and I've made a start on the ticketing part of it. Folks will be able to do their bug tracking in Project HQ at the end of this.

At the moment I've got the adding of tickets working. The next part to get working is viewing/updating. I've modeled the ticketing mostly after a combination of Trac and Launchpad, while taking a little inspiration from other issue tracking software like RT and the commercial JIRA (which we use at my day job).

 

Next Step: Bug Tracking

For me, a project management system is not complete without a bug tracking system. So my next step is to implement bug tracking in Project HQ. I've looked at a few bug/issue tracking systems, and I've decided to model mine after the one in Trac.

So far, I have completed the database design, and my next step is to start implementing the bug tracking in Project HQ. Thanks to SQLAlchemy I don't have to actually worry about creating the tables, as they are created when I do a "web setup."

 

Too late!

Oh dear, I found a rather wide-reaching bug in my code just after I released version 0.1.1!

Some new code I created to handle catching of unauthorised users has a flaw in it, which unfortunately affects most of Project HQ. I have fixed it in the Subversion repository already, but I'll release a new version in the next day or so.

I've also started adding a wiki to the system, so the above release will have to wait till I have the initial wiki code ironed out a little (should be, as mentioned above, in the next day or so).