First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:

• Use attributes Ticket and Status
• Preset Ticket with a running ticket number via
  
  Preset ticket = TCK-#####
  

  This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply

• Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)

  Options Status = open, closed
  Preset Status = open

• Once a ticked chain is closed, do the following:

  • Go to the threaded list display
  • Click on Select
  • Select the trouble ticket chain
  • Click on Edit
  • Now change Status from "Open" to "Closed"

This will then modify the Status of the whole chain from "Open" to "Closed"

> I installed the latest version (2.7) of ELOG and having the problem that the quick filter only works when hitting the 
> enter-key when there is only one free text field (subtext). Whene having two or more free text field you have to use 
> the tab-key or click onto the elog icon. We are using Internet Explorer, not tested on Mozilla right now.

I found that this is indeed an Internet Explorer bug, since it works with all other browsers I tested. There is however a
workaround: I added some code to the current version of elog which shows a "Search" button whenever the page is accessed
through the Internet Explorer. Then the behavior of hitting <return> works again. The change is in revision #1970 and will
be contained in the next release.

I fixed this in svn revision #1971. The fix will be contained in the next release. You can test it already in the demo logbook.

Ok, that's fixed now as well.

You cannot put the images into a subdirectory. The above link "pictures/ln2.jpg" will translate into a URL

http://<your server/pictures/ln2.jpg

and there the path pictures will be taken as a logbook name, and the server will complain that this logbook does not exist. Unfortunately you cannot see this error message since it happens during the loading of the picture, and the browser just displays a broken picture link. So put your image into the root of the elogd server and it will be fine.

I implemented this request in SVN revision #1974.

This is possible since the beginning: Click on Find, then check Display full entries and Printable output and hit Search. You get then a single page containing all entries from the logbook which you can easily print to get a hardcopy.

That sounds really strange. The only thing I can think of is that the demo entry conflicted with your other entries and two of them have the same entry ID. The entry ID is a unique key which identifies each entry. If you look into the raw logbook file 011108a.log with a text editor, you will see them as

$@Mid@$: 1
Date: Thu Nov 08 18:37:57 2001
Author: Stefan Ritt
Type: Routine
Category: General
Subject: Welcome
Attachment:
Encoding: ELCode
========================================
[B]Congratulations for installing ELOG sucessfully!
[/B]

This is a demo entry to ensure the elogd server is working correctly.
Click [I]"New"[/I] to add new pages and [I]"Delete"[/I] to delete this page.

so in this case the ID is 1. When you rsync'ed your entries into the demo logbook directory, you probably got two entries with the ID 1, which screws up elogd. Try to delete the file 011108a.log before you do the rsync. If you start elogd interactively with the "-v" flag, you will see some debugging output which can you help identify some problems:

[ritt@pc5082 ~/elog]$ ./elogd -v
elogd 2.7.0 built Dec 13 2007, 08:05:12 revision 1977
Config file  : /afs/psi.ch/user/r/ritt/elog/elogd.cfg
Resource dir : /afs/psi.ch/user/r/ritt/elog
Logbook dir  : /afs/psi.ch/user/r/ritt/elog/logbooks/
Indexing logbook "demo" in "logbooks/demo/" ...

Config [demo],                           MD5=F2E39262960C779517FEE576C17B1ED0

Entries:
  ID   1, 011108a.log, ofs     0, thead, MD5=81D89C3C94C6626BB7FF191026040E83
After sort:
  ID   1, 011108a.log, ofs     0
ok
Server listening on port 8080 ...