-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/19/10 13:18 , Steven Siebert wrote: > > > On Thu, Aug 19, 2010 at 5:44 AM, Jan Goyvaerts > <[email protected] <mailto:[email protected]>> wrote: > > Hi, > > Is there somebody in here who has practical experience in logging > automatically Jira tickets based on stack traces ? We're monitoring > the exceptions and mailing them. Better would be to log a ticket > automatically on Jira and if its exception matches an exception of > an existing ticket, it should mark the new ticket as a duplicate of > the original. > > This way we're not spammed and we get an idea of how the various > issues and how dire they are. > Never done, but sometimes wondered about that. What I've thought is:
1. Add a custom field to your JIRA (a string) 2. Compute the md5 of the exception dump. 3. Before filing a new issue, search for existing ones having the same md5 (or open the issue, then search for existing one and mark as duplicate). I'm not 99% sure but I think that the web services interface should allow to do search by custom fields. - -- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." java.net/blog/fabriziogiudici - www.tidalwave.it/people [email protected] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxtTVAACgkQeDweFqgUGxc1FACgm0OGGogSN8Fn4yTzl9xw7dk6 m0wAnjc1OXvNhxvBrTLik6PH0KP/gQDe =ebCW -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
