The main functionality of the Bug Tracker is managing bug reports.  The way that we’re handling this means that each entry in the Bug Tracker weblog is an actual bug report.

Now that we have the templates setup, the next step is to output a basic list of entries.  It’s time to begin working with the data that we’ve previously entered.

Onwards!

Lisa,

Very cool. I got to where you’ve taken us to this point in the tutorial ... and ... with a sad feeling from having to break off from the EE-momentum I built up ... I was wondering if your ultimate objective with this tutorial is for us to have the same bug tracker functionality as the EE one at http://expressionengine.com/bug_tracker/.

As I mentioned to you before, this type of tutorial is great because it gives essential insights into the methods of EE, and winds up with an important tool to use going forward.

Thanks again for this important work you’re offering ... and I look forward to the next installments of Bug Tracker!

Ramone

Hi, Ramone,

My intention here is to highlight a way that you can run a bug tracker, and some neat ways to manipulate that data.  Some of this will mirror what is in or Bug Tracker for ExpressionEngine, and some may be different. 

The idea is that ultimately, you can take these methods and use them on your own sites, for your own applications.  =)

That is the beginning, and from here, we can manipulate our entry list in a variety of interesting ways, as we’ll see in the upcoming articles.

Lisa, do you have a sense of when you’ll be releasing additional lessons of this tutorial? I don’t mean to pester, but I’m beginning an EE project that would benefit hugely from having a functional bug tracker. And if this tutorial is a lower priority and not slated for further development for a while, I’ll just use something like iCal’s ‘To Do list’ in the meantime.

Thanks.

Usually Thursday afternoon/evening.