There are several options:

• Use a bookmark in your browser. Put a link directly "Punch" and "Maintenance" in the link list of your browser and you can directly jump to that logbook. Different users can define different bookmarks in their browsers.
• Change the order of the logbooks in the group, like put "Punch" to be the first one in your group. But if you have different users with different permissions this will of course not work for all.
• Give up groups and just keep a linear list of logbooks. 

2. is not possible. Even if you use "Protect selection page", you will always be redirected to the first logbook after logging in. Maybe I should change that.

I generally consider using the ID as ticket number a bad idea. The ID is the "primary key" (in terms of database language), and must be unique inside a logbook. So when moving entries between logbooks, there will be always problems.

Why don't you define an attribute "Ticket ID" and use that one? That won't change when you move the entry between logbooks:

Attributes =  Ticket ID, Subject, ...
Preset Ticket ID = ID-#####

Why do you move the last ticket in a logbook at all? The move functionality was more meant as an archive option, where you can archive old entries on an annual basis or so. If you just want to "close" a ticket for example, an attribute "Status" with options "open" and "close" will do it. Together with a quick filter you can easily show only open entries in an logbook that way.

Stefan 

> Hi all, 
> 
> Is it just my system or do others have this odd issue.
> 
> I have a pdf file which is 'upside-down', I attached it to an elog entry, and the .png image thumbnail was
> generated.  Now this too was upside-down, so I tried to use the left (or right) rotation buttons along the top
> of the image in elog to do a 180 degree rotation.
> The first 90 degree rotation was fine, but the second attempt just made a smaller image.  
> It happens with various pdf files generated by various software (in case).
> I also tried it with a jpg file, in that case the second attempt enlarged the image.
> 
> I could not find any way to actually invert the .png image using elog; but I was surprised that a second
> rotation ddid something different (change magnification) rather than nothing at all if it could only cope with a
> 90 degree rotation.
> 
> It's not a vital fix for me, but I have found the thumbnail (png) manipulation functions have a few rough edges,
> so when necessary I use xv or gimp on the .png file to get what I want.
> 
> Or is this just my system?

I just tried on the demo logbook:

https://midas.psi.ch/elogs/Linux+Demo/14

and it worked fine in rotating the image twice. Can you try yourself and find out if it's related to your installation if ImageMagic, or the actual image file?

/Stefan

> Well I didn't crash the server this time, and I could invert the image in the demo logbook by doing two rotations.
> But, this is elog v2.9.0-2435, and I am using v2.9.2-2475.  And I remember there was a recent issue about the image manipulation at some point, so I went to the
> download section to read the subversion listing to find where this occurred.  But you've changed subversion!  I couldn't find my way around it, so I not only could
> I find the changefile that showed what happened for each subversion issue, but even how I could download the current (or indeed any past) subversion issue.
> 
> As far as I can recall, you made a change, I reported an issue, and you undid the change, or partially undid it.  Do you know when this was?  Could it be relivent?

I upgraded to V2.9.2, so please try again.

/Stefan

With

allow <command> = <user list>

deny <command> = <user list>

you can prevent certain users to use certain commands (like delete a message). If you only allow admins to issue the "edit" command, that would in principle do it, but then normal users cannot edit their entries any more. Unfortunately this command cannot be restricted to certain attributes, like the thread "status". So I guess what you want is not exactly possible with the current implementation. 

That's a different meaning. The "Locked by" flag gets set when one user edits an entry. During the editing the entry gets "locked", which means that no one else can change it during that time. This should prevent one person to overwrite the edits of another if they are editing the same entry at the same time. Your "locking" means the locking of threads, which elog doe not "understand", it's just your definition of an attribute in your logbook. 

Certainly 2.9.1 and 2.9.2 should behave similar in that respect. Have you tried to clear all cookies in your browser and try again?

/Stefan