$long_name in Moptions, posted by Fergus Lynch on Mon Nov 20 16:23:37 2006
|
Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list.
Thanks
Fergus |
Re: Re: $long_name in Moptions, posted by Stefan Ritt on Mon Nov 20 22:20:22 2006
|
| Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
|
Re: Re: $long_name in Moptions, posted by Fergus Lynch on Tue Nov 21 09:44:30 2006
|
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
WowThat was quick, I'll implement this morning. Many thanks for introducing this, ELOG is such a good tool.
Many Thanks
Fergus |
|
Re: Re: $long_name in Moptions, posted by Fergus Lynch on Tue Nov 21 11:14:48 2006
|
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
Hi Stefan, apologies if I am being a bit dense (!) When I download the latest windows binary it extracts to ELOG V2.6.2-1749. Where could I get revision 1758 >
Thanks in advance
Fergus |
Attributes according to users, posted by ather khan on Sat Nov 18 11:19:14 2006
|
Hi,
Is it possible to have certain attributtes available to certain user in one log boolk.
We have log book where the supervisor assign jobs to employees and we want only supervisor to have assign to attributes available and others only to view it.
thanks,
Ather |
|
Re: Attributes according to users, posted by Stefan Ritt on Sat Nov 18 17:13:22 2006
|
| ather khan wrote: | Hi,
Is it possible to have certain attributtes available to certain user in one log boolk.
We have log book where the supervisor assign jobs to employees and we want only supervisor to have assign to attributes available and others only to view it.
|
You cannot restrict the modification if certain attributes, but you can restrict edits in general with the command
Allow edit = <name of admin>
You can also restrict the New, Delete, etc. commands to be only executable by the supervisor. |
add field type to automatically email CC, posted by Mark Bergman on Thu May 25 19:41:51 2006
|
I've got logbooks where I'm submitting entries on behalf of other users, or where other people should be notified of the ticket. This isn't a fixed list of people, and shouldn't be hard-coded into a config file. I've got a field to enter the user's e-mail address, but there's no action associated with that data.
I'd like to see a new field type that allows the entry of e-mail addresses, where each addresses supplied with the logfile entry would be automatically "CC'ed" in the notification e-mail. Ideally, people on the CC list would be (optionally) CC'ed when there are replies or edits to the original elog entry.
For example (snippet of fictional elogd.cfg):
-------------------------------
[web site]
Welcome Title = Issues regarding the web site
MOptions Category = Add links, Change content, Broken Link, Other
CCMailTo = Notification List
Attributes = Author, Category, Severity, Subject, Entry ID, Status, User, Login
Extendable Attributes = Category, Severity, Subject, Status, User, Login, Notification List
Required Attributes = Category, Subject, Status, User
------------------------------- |
|
Re: add field type to automatically email CC, posted by Stefan Ritt on Thu Nov 9 22:08:10 2006
|
| Mark Bergman wrote: | I've got logbooks where I'm submitting entries on behalf of other users, or where other people should be notified of the ticket. This isn't a fixed list of people, and shouldn't be hard-coded into a config file. I've got a field to enter the user's e-mail address, but there's no action associated with that data.
I'd like to see a new field type that allows the entry of e-mail addresses, where each addresses supplied with the logfile entry would be automatically "CC'ed" in the notification e-mail. Ideally, people on the CC list would be (optionally) CC'ed when there are replies or edits to the original elog entry.
For example (snippet of fictional elogd.cfg):
-------------------------------
[web site]
Welcome Title = Issues regarding the web site
MOptions Category = Add links, Change content, Broken Link, Other
CCMailTo = Notification List
Attributes = Author, Category, Severity, Subject, Entry ID, Status, User, Login
Extendable Attributes = Category, Severity, Subject, Status, User, Login, Notification List
Required Attributes = Category, Subject, Status, User
------------------------------- |
Just do the following:
Attributes = Author, Category, Notification list
Email all = $Notification list
Whenever you enter a new entry, you put a list of email addresses into the Notification list, which is then used for sending email addresses. This list also stays there in replies or edits. |
|
Re: add field type to automatically email CC, posted by Arckonit on Wed Nov 15 18:50:02 2006
|
| Stefan Ritt wrote: |
| Mark Bergman wrote: | I've got logbooks where I'm submitting entries on behalf of other users, or where other people should be notified of the ticket. This isn't a fixed list of people, and shouldn't be hard-coded into a config file. I've got a field to enter the user's e-mail address, but there's no action associated with that data.
I'd like to see a new field type that allows the entry of e-mail addresses, where each addresses supplied with the logfile entry would be automatically "CC'ed" in the notification e-mail. Ideally, people on the CC list would be (optionally) CC'ed when there are replies or edits to the original elog entry.
For example (snippet of fictional elogd.cfg):
-------------------------------
[web site]
Welcome Title = Issues regarding the web site
MOptions Category = Add links, Change content, Broken Link, Other
CCMailTo = Notification List
Attributes = Author, Category, Severity, Subject, Entry ID, Status, User, Login
Extendable Attributes = Category, Severity, Subject, Status, User, Login, Notification List
Required Attributes = Category, Subject, Status, User
------------------------------- |
Just do the following:
Attributes = Author, Category, Notification list
Email all = $Notification list
Whenever you enter a new entry, you put a list of email addresses into the Notification list, which is then used for sending email addresses. This list also stays there in replies or edits. |
mmmm when i try your suggestion, it doesn't work :
error from the smtp server
Erreur lors de l'envoi d'un mél. via "172.20.0.2": Issue RCPT TO: command before DATA command
here is my configTheme = default
Comment = Logs des modification de scripts des 3 domaines
Attributes = Acteur, Action, Type, Nom du Scripts, Language, Domaine, Categorie, Commentaires,Notification
Options Action = Ajout, Modification, Suppression, Réseau, Autre, Hotfix
Options Type = Ouverture de session,Autre, deploiement
Options Language = VBS, AU3, Kix, Batch, Ksh, Perl
Options Domaine = VaubanHumanis, Humanis, Vauban
Extendable Options = Catégorie, Type, Action
Required Attributes = Acteur, Type, Lieu
Page Title = Modification Scripts - $subject
Reverse sort = 1
Quick filter = Date, Type
Suppress Email to users = 1
# Email all = someadminsuser@maildomain.com
Email all = $Notification
Options Status = 1-To Do{1}, 2-Open{2}, 3-Closed{3}, 4-Suspended{4}
you can remark the commented line
i would like to have one fixed list, so those users will be always alerted, and to be able to add and adress email in the notification attribute, but i really don't know how to do it
thx for any suggestions |
|
Re: add field type to automatically email CC, posted by Stefan Ritt on Wed Nov 15 19:33:17 2006
|
| Arckonit wrote: | mmmm when i try your suggestion, it doesn't work :
error from the smtp server
Erreur lors de l'envoi d'un mél. via "172.20.0.2": Issue RCPT TO: command before DATA command |
You get this error if no valid receiver is specified. I tried your config file and it worked fine. You need however a recent version of elog (2.6.2-7). Probably you have to upgrade.
| Arckonit wrote: | you can remark the commented line
i would like to have one fixed list, so those users will be always alerted, and to be able to add and adress email in the notification attribute, but i really don't know how to do it
thx for any suggestions |
You can do that with
Preset Notification = someone@mail.com, someoneelse@mail.com
So Notification gets preset with a pre-defined list, which you can edit before submission. |
|
Report printing, posted by Eric Krise on Mon Nov 13 18:10:42 2006
|
| Is there a way to print a summary of all (or selected) log books on a scheduled basis, say like every morning @ 7:00 am? I would like a printed copy of our daily logs (24 hr period). Thanks Eric |
|
Re: Report printing, posted by Stefan Ritt on Mon Nov 13 20:22:02 2006
|
| Eric Krise wrote: | | Is there a way to print a summary of all (or selected) log books on a scheduled basis, say like every morning @ 7:00 am? I would like a printed copy of our daily logs (24 hr period). Thanks Eric |
You can obtain the last 24hr period with the parameter last=1. Following command will return this last day for the forum
http://midas.psi.ch/elogs/Forum/?printable=1&last=1
Now you need to set up some script which calls this once a day and then convinces the browser to print that page. But I have no idea how to perform this.
Another option is to print the xxxxxxa.log files of the elogd server directly. There is already one file per day, and the original reason for that is exactly what you ask for: You can print each day directly. Now you need a script which searched for the last day and prints that. |
Outlook, Outlook Express and Free Webmail have problem with <br />, posted by An Thai on Thu Nov 9 23:52:26 2006 
|
If users reply an entry, the notification email cannot be displayed correctly in Outlook, Outlook Express and Webmail.
I look at the source code and see <br />. It could be the reason. |
|
Re: Outlook, Outlook Express and Free Webmail have problem with <br />, posted by Stefan Ritt on Fri Nov 10 07:46:27 2006
|
| An Thai wrote: | If users reply an entry, the notification email cannot be displayed correctly in Outlook, Outlook Express and Webmail.
I look at the source code and see <br />. It could be the reason. |
<br /> is XHTML standard and valid code. I do not have this problem in Mozilla Thunderbird. |
|
Re: Outlook, Outlook Express and Free Webmail have problem with <br />, posted by Steve Jones on Fri Nov 10 12:55:38 2006
|
| Stefan Ritt wrote: |
| An Thai wrote: | If users reply an entry, the notification email cannot be displayed correctly in Outlook, Outlook Express and Webmail.
I look at the source code and see <br />. It could be the reason. |
<br /> is XHTML standard and valid code. I do not have this problem in Mozilla Thunderbird. |
| Quote: |
I've noticed teh same in Outlook and attribute it to MS' attempt to deal with HTML -- this was not an issue until a recent Outlook upgrade at our company.
The problem is with Outlook and MS' email clients.
|
|
|
Option to require new user registration to subscribe to ALL logbooks, posted by Steve Jones on Mon Nov 6 19:03:11 2006
|
Stefan, any chance of having an option that eliminates the ability of new users to pick the logbooks they can register with? I would like to limit this to the "admin" user to pick per individual.
Also, any thoughts to adding a management panel that will the admin user to make global changes to the password file? I do this by bringing it into a text editor and making changes, but it would be nice to do it from the application. |
|
Re: Option to require new user registration to subscribe to ALL logbooks, posted by Stefan Ritt on Thu Nov 9 22:57:38 2006
|
| Steve Jones wrote: | | Stefan, any chance of having an option that eliminates the ability of new users to pick the logbooks they can register with? I would like to limit this to the "admin" user to pick per individual. |
The logbook list new users can register with is exactly the list the users have access to. So if you omit a logbook there, they can later just go to that logbook, hit config, and add themselves. If you want to prevent a user from getting notifications from a logbook, prevent user access to that logbook, like a new top group.
| Steve Jones wrote: | | Also, any thoughts to adding a management panel that will the admin user to make global changes to the password file? I do this by bringing it into a text editor and making changes, but it would be nice to do it from the application. |
Not at the moment. It would take days of work which I don't have right now. Much more than what it takes you editing the password file in an editor  |
|
Re: Option to require new user registration to subscribe to ALL logbooks, posted by Steve Jones on Thu Nov 9 23:37:37 2006
|
| Stefan Ritt wrote: |
| Steve Jones wrote: | | Stefan, any chance of having an option that eliminates the ability of new users to pick the logbooks they can register with? I would like to limit this to the "admin" user to pick per individual. |
The logbook list new users can register with is exactly the list the users have access to. So if you omit a logbook there, they can later just go to that logbook, hit config, and add themselves. If you want to prevent a user from getting notifications from a logbook, prevent user access to that logbook, like a new top group.
| Steve Jones wrote: | | Also, any thoughts to adding a management panel that will the admin user to make global changes to the password file? I do this by bringing it into a text editor and making changes, but it would be nice to do it from the application. |
Not at the moment. It would take days of work which I don't have right now. Much more than what it takes you editing the password file in an editor |
| Quote: |
Hmm, by default all users have access to all logs. What I have setup is an announcement logbook and I would simply like to send to all registered users the email when announcements happen. My thought was to simply not allow people to pick which logbooks to "register" with and default to the Announcements logbook. I went ahead and hacked the password file and simply set all accounts to subscribe to all logbooks 
|
|
|
How can I configure to prevent empty entries?, posted by Alan Stone on Mon Apr 10 20:28:37 2006
|
I have accidentally created a couple of entries recently. It is pretty easy. I
fill in the header, type in a Subject, and then hit Enter, instead of TAB.
I have turned off the edit option intentionally.
I want to avoid this in the future. Is there a configuration option which would
confirm that the user before submitting an entry without a Body? I know I can require
attributes like Author and Subject. I am not sure I want to require a Body, in case
someone submits an entry with just an attachment (and a Subject).
Thanks, Alan |
|
Re: How can I configure to prevent empty entries?, posted by Stefan Ritt on Thu Nov 9 23:10:08 2006
|
| Alan Stone wrote: | I have accidentally created a couple of entries recently. It is pretty easy. I
fill in the header, type in a Subject, and then hit Enter, instead of TAB.
I have turned off the edit option intentionally.
I want to avoid this in the future. Is there a configuration option which would
confirm that the user before submitting an entry without a Body? I know I can require
attributes like Author and Subject. I am not sure I want to require a Body, in case
someone submits an entry with just an attachment (and a Subject).
Thanks, Alan |
Actually the submit/edit behavior is controlled by your browser, not by elog. I do not know any mean of how the HTML code could control this independently of the browser. So you have to get used to it |
|
Is it possible to require certain attributes for specific users (guests)?, posted by Mark Bergman on Tue May 2 22:58:48 2006
|
First of all, thanks for writing and maintaining eLog.
I've been using it for a few years, but I'm now introducing it in an environment that may have a lot of "Guest"
accounts.
I'd like to have two "Required Attributes" when a guest enters a new entry; their name and e-mail address. These
fields don't need to be required for registered accounts, since that information is available already.
Is there any way to have conditional statements act on the value of $short_name?
Thanks,
Mark |
|
Re: Is it possible to require certain attributes for specific users (guests)?, posted by Stefan Ritt on Wed May 3 08:31:52 2006
|
> First of all, thanks for writing and maintaining eLog.
>
> I've been using it for a few years, but I'm now introducing it in an environment that may have a lot of "Guest"
> accounts.
>
> I'd like to have two "Required Attributes" when a guest enters a new entry; their name and e-mail address. These
> fields don't need to be required for registered accounts, since that information is available already.
>
> Is there any way to have conditional statements act on the value of $short_name?
No, this is not implemented. The only way you have right now is to make two separate logbooks, one for guests and
one for registered users. But I know this is not an optimal solution. I will think about it. |
|
Re: Is it possible to require certain attributes for specific users (guests)?, posted by Stefan Ritt on Thu Nov 9 23:04:32 2006
|
> First of all, thanks for writing and maintaining eLog.
>
> I've been using it for a few years, but I'm now introducing it in an environment that may have a lot of "Guest"
> accounts.
>
> I'd like to have two "Required Attributes" when a guest enters a new entry; their name and e-mail address. These
> fields don't need to be required for registered accounts, since that information is available already.
>
> Is there any way to have conditional statements act on the value of $short_name?
>
> Thanks,
>
> Mark
Actually there is one possibility:
Preset Author = $long_name
Required Attributes = Author
This will force the author to be supplied. If one is logged in, the login name will be put into the author field. If
there is guest access, the field will contain "anonymous", so hopefully each guest will change that to the real name... |
|