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.

[demo]
Theme = default
Attributes = Ticket, Author, Subject
Preset Ticket = TCK-####

The the first entry gets TCK-0001. Any reply to that stays with TCK-0001. Then I do another "new" entry, which gets TCK-0002. Even if I then do another reply to the first thread, that will just stay with TCK-0001. So avoid using 'Preset on reply Ticket". The post from Richard was different, he wanted a new number also for replies (if I understand correctly).

Preset ticket = TCK-#####

Preset on reply ticket = TCK-#####

When I was browsing this forum about my previous problem, I found 
this thread. A ticket number that applies to all entries in a 
thread, but is unique to that thread.

But I have the same problem as Richard Ecclestone reported, and the
"Preset on reply ticket" line from your reply has not had any effect.

It appears that on starting a new thread (which is to have that
ticket number), the ticket number is just incremented by one from
that of the previous (as in previous ID number) entry.  This is
fine if each thread is completed before a new one started, but if
there are more than one active thread, which can be progressed
further in any order, new threads are likely to be issued with a
ticket number which has already been issued (see Richards's example).

An alternative source of unique numbers would be the Entry number (as
in "696 Entries", top right of the midas.psi.ch/elogs/Forum page),
which would be the seed for the ticket number on new entry.  Not sure
of the syntax for that, or for the replies to have *that* number for
the config file.  I know there is a problem if you move a number of
threads away, but the only alternative (that I can think of) is to
store the seed number somewhere, and increment it every time a new
thread is started.

Or have I got something wrong here? 
Thanks.

Regards,

David.

I found the answer in the docs.

In the config file add

Use Email Subject = Added Text: $subject

This results in the e-mail subject being set to "Added Text: elogentry subject line"

Thanks for a great tool!

Can I control the content of the Subject on an email notification?

i.e. Can I copy the subject from the elog entry into the email subject?

Thanks,

//Bill

> > Hi,
> > 
> > I've just upgraded from 2.6.2 to 2.7.3.
> > 
> > In my config file, I have
> > 
> > Quick filter: Date, ID.
> > 
> > When starting 2.7.3, across the top I now get 
> > 
> > "Error: Attribute "ID" for quick filter not found"
> > followed by an entry box.
> > 
> > If an ID is typed into that box, it sort of finds the right entry (+/- a few on occasion).
> > 
> > I cannot see any documented change that would affect how the Quick filter works.  Any clues?  Thanks.
> 
> Actually it is nowhere written the 'ID' for a quick filter should work. After investigating, I realize that it
> worked previously "by accident". I added in meantime some test so there is a warning for quick filter attributes
> which do not exist, and that's what you got. I loosened this test for 'ID' now in the current SVN version, so it
> can be used. It does however not display the single entry you want, but a page containing that entry (which then
> is displayed in bold). If you want exactly one entry, just add it's ID to the URL, like
> 
> https://midas.psi.ch/elogs/Forum/65767
> 
> for your previous entry.

Thanks Stefan!