Software, Development, and WordPress

Using LighthouseApp For WordPress Issues

One of the things that I love about GitHub is how they’ve done a great job integrating source code, milestones, tickets, pull requests, and so on.

But if you’re working with WordPress, not all projects all on which you work will use GitHub.

Case in point: If you’re selling a theme on or if you’re working on a plugin that is hosted in the WordPress Plugin Repository, then you’re going to be using Subversion as your source control system. But this doesn’t mean that you have to sacrifice the work flow of milestones, tickets, and so on.

It just requires that you use a third-party solution. For example, for the past couple of months, I’ve been using LighthouseApp as my issue tracker of choice for Mayer.

LighthouseApp For Issues

I know that there are some developers who like to sync their GitHub repository with a Subversion repository in order to take advantage of the aforementioned features – and that’s great!

But my personal workflow is a little bit different depending on how the code is managed via source control. In this case, since the theme is primarily kept in Subversion, then I don’t want to duplicate it across multiple locations (which is partially related to what I discussed in the previous post).

To that end, I’ve opted to use another solution for tracking issues.

LighthouseApp For WordPress

As touted on the LighthouseApp homepage:

Beautifully Simple Issue Tracking

Collaborate effortlessly on projects. Whether you’re a team of 5 or studio of 50, Lighthouse will help you keep track of your project development with ease.

And I have to agree  – the web application is a no frills solution to creating milestones, setting due dates, creating tickets, and so on for managing your project.

No, it’s not a source code solution, but it’s meant to compliment exactly that – I love simple, focused applications just like that.

Using Lighthouse For Mayer

Up to this point, I used Lighthouse to manage tickets for Mayer for three released milestones (namely 1.0.0 to 1.4.0 and I’m using it to plan tickets for 1.5.0.

LighthouseApp For Mayer

For those who are coming from a separate solution, the most important thing to remember is that Lighthouse is meant specifically for tickets – that is, it’s meant to track bugs and other potential issues that exist within your project.

Lighthouse is not a support forum application (luckily, provides that).

That said, my favorite features are as follows:

  • Creating milestones and optionally setting due dates
  • Including collaborators in in your project
  • Tagging tickets based on their priority
  • Being able to comment on each ticket using markdown
  • Support for attaching screenshots and other files relevant to the ticket.

There’s more that the application can do, but those are the features that I use the most.

So if you’re in the market of looking for a solid issue tracker for your WordPress theme (or any project, really) then I highly recommend taking a look at LighthouseApp.

It’s a great, easy-to-use solution, integrates well into any workflow that’s used to the milestone-ticket-resolution procedure, and also makes it as simple as possible to enter the relevant information as possible.


  1. Harish

    Hey Tom, check this too

    • Tom

      Thanks Harish — they’ve got a slick site, for sure. I’m also always on the lookout for other options, though right now Lighthouse seems to be fitting the bit quite nicely.

  2. Japh

    I’ve used Lighthouse in the past too. I did’t mind it, but I didn’t love it either.

    I’m curious too… considering Lighthouse is uncoupled from your version control software, what made you choose that over just creating an empty private GitHub repo so you could use Issues? (I’ve heard of organisations who run everything through GitHub, and I believe this is their approach to non-source related issue management)

    • Slobodan

      That was my first thought, too, especially if you’re already using Github.

      I tried LighthouseApp a few years ago, all I remember is that I didn’t mind it.

    • Tom

      I’ve used Lighthouse in the past too. I did’t mind it, but I didn’t love it either.

      I can totally see that. It’s not as beautiful as some applications, as it’s not as feature-rich of others, but that’s why I like it — it just exactly what I’d like it to do and nothing more.

      It works well with my current workflow.

      what made you choose that over just creating an empty private GitHub repo

      Limitations on my current plan :).

  3. John Mann

    I’ve seen so many, and I’m always a fan of simple over feature-rich.
    Mashable put together a pretty comprehensive list, but each I’m sure has their own wins:

    I’m going to try Lighthouse for my next project and see how it goes.
    Thanks for the suggestion.

    • Tom

      I’ve seen so many, and I’m always a fan of simple over feature-rich.

      Exactly! I think there are some areas in which the UI could be improved, but – as with anything – once you learn it, you’re good to go.

      Thanks for the link, too. I appreciate it – always glad to have resources to which I can refer.

Leave a Reply

© 2020 Tom McFarlin

Theme by Anders NorenUp ↑