ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65767
|
Tue Mar 4 14:03:00 2008 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 2.7.3-2058 | Quick filter by ID | 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. |
65769
|
Thu Mar 6 14:12:28 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.3 | Re: German language |
Salvatore wrote: |
Wen es interessiert:
der Eintrag "eloglang = german" gehoert in das Verzeichnis "usr/lib/elog/resources". Dort wird er von elogd ausgelesen.
|
Wie bitte ist der dorhin gekommen? Normalerweise wird elogd.cfg unter /usr/local/elog gespeichert. Wenn man natuerlich diese Datei von Hand irgendwo andershin kopiert, muss man sie auch dort veraendern, sonst schiesst man sich selbst in's Bein. |
65770
|
Thu Mar 6 15:06:35 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.3-2058 | Re: Quick filter by ID | > 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. |
65774
|
Fri Mar 7 13:12:37 2008 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 2.7.3-2058 | Re: Quick filter by ID | > > 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! |
65775
|
Fri Mar 7 13:44:34 2008 |
| Bill Whiting | textux@bellsouth.net | Question | Linux | 2.7 | email subject | 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 |
65776
|
Fri Mar 7 14:09:40 2008 |
| Bill Whiting | textux@bellsouth.net | Question | Linux | 2.7 | Re: email subject |
Bill Whiting wrote: |
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
|
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! |
65780
|
Fri Mar 7 21:26:18 2008 |
| David Pilgram | David.Pilgram@epost.org.uk | Info | Linux | ELOG V2.7. | Re: Message ID and trouble ticketing system | >Stefan Ritt wrote:
>
>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.
----
Great! Thanks Stefan, off to download right now!
Great program, by the way, but don't think you need to be told that yet again! |
65781
|
Fri Mar 7 21:53:28 2008 |
| David Pilgram | David.Pilgram@epost.org.uk | Info | Linux | 2.7.3-2073 | Re: Message ID and trouble ticketing system | >>Stefan Ritt wrote:
>>
>>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.
>
>----
>
>Great! Thanks Stefan, off to download right now!
>
>Great program, by the way, but don't think you need to be told that yet again!
---
Oh ho!
I've tried this on an existing database, where most entries do not have a ticket #. The previous entry #
(previous in ID sense) is T00550, say. But when I start a new thread, the ticket # is T00001. Is it being put
out by no entry for ticket # in most of the database?
LATER UPDATE.
On a small database (12 entries, with 45 comments in total), this worked as expected if most or all entries have ticket numbers, even if the previous (by id #) had not had a ticket number. (I had to edit every entry to put in ticket numbers).
The only thing I can think of is the number of entries that don't have a ticket #, or a line in the .log file entry saying "Ticket: " but am looking further into this.
(BTW, am posting this way to get around the proxy server problem I have!) |
|