Sending errors to your ticketing system

I’ve been thinking about developing a PHP Logger that will talk to your favorite ticketing system. The idea is to capture code and application generated errors and create tickets accordingly.

At a first glance, I could use the Reflection API to get meta-information about the code. Tickets could then be created and assigned to the appropriate person based on the @author doc tag.

The ticket Logger could talk to existing Web project management and ticketing application like Basecamp, Goplan and Hiveminder (from the creators of RT).

Do you think you would benefit from this type of Logger? What ticketing system are you using on your own projects?

Advertisements

3 thoughts on “Sending errors to your ticketing system”

  1. I think this is a great idea.

    Just one note though …

    “At a first glance, I could use the Reflection API to get meta-information about the code. Tickets could then be created and assigned to the appropriate person based on the @author doc tag.”

    We live in a mutable world. At first glance I loved this idea but then I start thinking “but there can be many authors, employees often change companies”, etc

    How do you propose to solve this kind of issues? 🙂

    Just my two cents 😉

  2. Usually the @author tag is filled up with a name and an e-mail address, right?

    Your concern makes sense, so here’s my solution. You can have two kinds of situations:

    1- You’re dealing with an external or outsourcing developer so you want to stick with his/her e-mail address on the @author tag. This way, if there’s a problem in the future the developer will be automatically contacted by the ticketing system.

    2- You’re dealing with an internal developer, so the e-mail address will something@yourcompany.com, right? If the developer leaves the company you can and should immediately create an forward of his/her e-mail address to someone else.

    I think the problem is not with this attempted implementation but with company policies regarding their employees.

  3. “You’re dealing with an external or outsourcing developer so you want to stick with his/her e-mail address on the @author tag. This way, if there’s a problem in the future the developer will be automatically contacted by the ticketing system.”

    I don’t think this would work. It would have to be forwarded also. One other option would be to have “someone” have to deal with this kind of “lost” tickets.

    Nevertheless … it’s a great ideia! 😉

What do you think?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s