Your message dated Sat, 29 Jul 2006 22:26:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line After upgrade from 1.3.2 to 1.3.2p01-6 no more email
notifications and error after new ticket
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: otrs
Version: 1.3.2p01-6
Severity: important
Tags: patch
After an upgrade from 1.3.2 to 1.3.2p01-6 no Agent Notification was sent
anymore when Tickets were entered in the Customer Web-Interface.
The following patch for /usr/share/otrs/Kernel/System/Ticket.pm
was successful for enabling the notification again:
Added the ## in
sub GetSubscribedUserIDsByQueueID
# check if user is valid and check permissions
my @CleanUserIDs = ();
foreach (@UserIDs) {
my %User = $Self->{UserObject}->GetUserData(UserID => $_, Valid => 1);
if (%User) {
# just send emails to permitted agents
##my %GroupMember = $Self->{GroupObject}->GroupMemberList(
## UserID => $_,
## Type => 'ro',
## Result => 'HASH',
##);
##if ($GroupMember{$Queue{GroupID}}) {
push (@CleanUserIDs, $_);
##}
}
}
return @CleanUserIDs;
Any idea what unwanted collateral damage this patch could cause?
Another error appeared after adding a new Ticket in the customer
Web-Interface about a wrong Encode package. With replacing
/usr/share/otrs/Kernel/System/Encode.pm Revision 1.10 by 1.10.2.1 from
CVS this could be fixed.
Both bugs are also entered in the OTRS bugtracker:
http://bugs.otrs.org/show_bug.cgi?id=1169
http://bugs.otrs.org/show_bug.cgi?id=1170
System is Standard Debian 3.1, with custom kernel 2.6.14.
--- End Message ---
--- Begin Message ---
No response from the submitter. That is why I am closing this bug
report now. Please reopen if necessary with more information.
Regards,
Torsten
--
http://www.twerner42.de/
--- End Message ---