Comments on: Sending errors to your ticketing system http://unfoldingtheweb.com/2008/01/29/sending-errors-to-your-ticketing-system/ A new way of using the web Mon, 11 Apr 2011 16:00:09 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Daniel Barradas http://unfoldingtheweb.com/2008/01/29/sending-errors-to-your-ticketing-system/comment-page-1/#comment-2019 Daniel Barradas Mon, 03 Mar 2008 22:30:58 +0000 http://unfoldingtheweb.com/2008/01/29/sending-errors-to-your-ticketing-system/#comment-2019 "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! ;) “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! ;)

]]> By: Bruno Pedro http://unfoldingtheweb.com/2008/01/29/sending-errors-to-your-ticketing-system/comment-page-1/#comment-2018 Bruno Pedro Thu, 14 Feb 2008 17:03:18 +0000 http://unfoldingtheweb.com/2008/01/29/sending-errors-to-your-ticketing-system/#comment-2018 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. 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.

]]> By: Daniel Barradas http://unfoldingtheweb.com/2008/01/29/sending-errors-to-your-ticketing-system/comment-page-1/#comment-2017 Daniel Barradas Tue, 12 Feb 2008 23:20:51 +0000 http://unfoldingtheweb.com/2008/01/29/sending-errors-to-your-ticketing-system/#comment-2017 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 ;) 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 ;)

]]>