Log in to Lighthouse
Tips / Tricks →
12 Dec, 2010 04:12 AM
Just wanted to share a lengthy new tutorial I wrote on
integrating Lighthouse and Beanstalk into your workflow. This
article is aimed at someone who is new to issue tracking, or is
simply fed of with boring ugly bug trackers!
How many bugs can you keep track of in your head at once? If you
are anything like me, that number is somewhere in the single digit
range. This is why issue tracking is a very important tool that
every programmer should be using now. There are tons of free issue
tracking programs like Mantis, Bugzilla, or even web based
applications like Lighthouse. There is no excuse to put it off any
longer if you aren’t already doing it. The reason it is
important to use issue tracking on every project is that you will
be more likely to produce a better product by fixing bugs before
you add new features. Tracking your issues also allows your clients
to see what you are doing on their projects and allows them to have
a better understanding of what their deadline and progress
expectations should be.
Frankly I think simplicity is best for issue tracking and
Lighthouse is the tool I use to handle all of my issue tracking for
every project I work on. It is a very simple, powerful and
beautiful issue tracker that allows for third party integration via
its API. This is great because you can commit files and the changes
will be attached to your tickets, like commits from GitHub or
Thanks for reading,
2 Posted by Will Duncan on 12 Dec, 2010 05:39 AM
Awesome. Thanks James! I'll probably post a link to this up on
3 Posted by jblotus on 12 Dec, 2010 07:01 AM
No problem and thanks for the link. I have a lot of love for
your app and I want to spread the gospel!
Nicole closed this discussion
on 20 Dec, 2010 04:08 PM.
Comments are currently closed for this discussion.
You can start a new one.
2 people watching.
No more actions from Lighthouse or the discussion starter are required.
This discussion is private.
Only you and Lighthouse support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
Powered by Tender™.