• ELOG allows you to have different commands for different users. You could allow "New" and "Edit" for normal users, but "Reply" only for administrators.
• You can use "Subst on reply <attribute> = <string>" to set a specifc fields only on reply. 
  • You would hide "status" & "assignee" for new entries or edit (Show Attributes Edit = <list>), and show a "set status" field instead.
  • The line "Subst on reply status = $set status" would take care, that only an administrator can set "status" with a reply to the original entry (+ a "set assignee" field, etc.). While normal users could set "set status", it would not change the "status" field. You could provide a comment or tooltip to explain that.
  • The list view or single entry view should not show the "set status", but only the "status" attribute (List display = <list>, Show Attributes = <list>).
• Use "Propagate attribute = status, assignee" to take care, that the original entry gets their fields set accordingly.

This is how you could do what you want. But bugzilla can do a lot more if you are looking for a bug tracking software.

Cheers, Andreas

Oups: there is a flaw in this approach! You can only get different commands for Anonymous and Login Users. You cannot select different command for Admin users: they will just have the "Config" command automatically.

You could allow anonymous users to make new entries and restrict login to administrators. But that is certainly not what you want, so forget my suggestion altogether.

I am honestly not sure if I understand the question. You can run ELOG behind an Apache Webserver. Look for example at https://midas.psi.ch/elog/adminguide.html#secure

Preset Author = $shell(if [ $short_name = "Anonym" ] ;then echo $Author;else echo \"$long_name, $Author\";fi)
It adds $long_name to the Author field for non-anonymous entries.

Cheers Andreas

I don't think that this is possible.

And it is not clear to me, how you would like it to work: I often use HTML tables in preset text, where the user should fill out columns (e.g. for checklists). I wouldn't want the tables just to append when switching to another checklist. You could rather add a comment to the Type field, explaining that the text field will be overwritten when you change the type.

The Firefox addon Lazarus does store whatever you've typed in an HTML form: at least you could then recover what you've typed.

Cheers, Andreas

> Hi there
> 
> Okay so let me explain what im trying to do. I have a table in a logbook (lets call it home) that the user fills
> out. This information in the table is related to other logbooks (8 of them to be exact).
> I want to propogate information from the table in the home logbook into the other logbooks. To do this I used
> Execute new which runs my scripts. One of the scripts makes a call to the elog
> client to submit the message. The problem is that this call to elog client never finishes because its hanging
> waiting for the initial submit (one which triggered Execute new) to finish. The documentation
> explained that only one submit can be processed at a time so i expected whats happening at the moment.
> 
> My question is are there any other ways to do what im trying to do?? In a nutshell how to propogate information
> from one logbook to another autonomously.
> 
> Regards
> Kenzo

Hi Kenzo,
I think it would help me to understand your problem, if you would provide a minimal configuration file with two
logbooks.

There is no ELOG internal feature to propagate data from one logbook to another; 
using a shell script is the only method I know.
But you could easily put your script into the background: 
ELOG can handle multiple parallel request, by handling one request after the other.

Kind Regards, Andreas