Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   Message ID and trouble ticketing system, posted by lance on Sat Nov 24 03:16:46 2007 
    icon2.gif   Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Mon Nov 26 14:33:59 2007 
       icon2.gif   Re: Message ID and trouble ticketing system, posted by lance on Mon Nov 26 16:58:26 2007 
          icon2.gif   Re: Message ID and trouble ticketing system, posted by Richard Ecclestone on Fri Feb 15 15:46:38 2008 
             icon2.gif   Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Thu Feb 21 08:04:50 2008 
                icon2.gif   Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 14:29:00 2008 
                   icon2.gif   Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 14:45:02 2008 
                      icon2.gif   Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 20:42:39 2008 
                         icon14.gif   Re: Message ID and trouble ticketing system, posted by David Pilgram on Fri Mar 7 21:26:18 2008 
                            icon5.gif   Re: Message ID and trouble ticketing system, posted by David Pilgram on Fri Mar 7 21:53:28 2008 
Message ID: 65781     Entry time: Fri Mar 7 21:53:28 2008     In reply to: 65780
Icon: Question  Author: David Pilgram  Author Email: David.Pilgram@epost.org.uk 
Category: Info  OS: Linux  ELOG Version: 2.7.3-2073 
Subject: Re: Message ID and trouble ticketing system 
>>Stefan Ritt wrote:
>>
>>Ok, now I got the point, also Richard had the same problem. Assume we have 10 threads, and thus
>>ticket numbers 1-10. Now we get a reply to #2, which then pops up to the top of the list. A new
>>message increments the top entry of all entries, and then wrongly gives a new #3, instead of #11.
>>
>>I fixed this in SVN revision 2073, where elogd searches *all* logbook entries for the largest
>>index, then increments this one by one. The fix will be contained in the next release.
>
>----
>
>Great! Thanks Stefan, off to download right now!
>
>Great program, by the way, but don't think you need to be told that yet again!

---

Oh ho!

I've tried this on an existing database, where most entries do not have a ticket #. The previous entry #
(previous in ID sense) is T00550, say. But when I start a new thread, the ticket # is T00001. Is it being put
out by no entry for ticket # in most of the database?


LATER UPDATE.

On a small database (12 entries, with 45 comments in total), this worked as expected if most or all entries have ticket numbers, even if the previous (by id #) had not had a ticket number. (I had to edit every entry to put in ticket numbers).

The only thing I can think of is the number of entries that don't have a ticket #, or a line in the .log file entry saying "Ticket: " but am looking further into this.

(BTW, am posting this way to get around the proxy server problem I have!)
ELOG V3.1.5-fe60aaf