Hi Alan,
On 12.08.2009, at 18:47, Alan McKay wrote:
Well, I have a compromise for now. I created a new event for
TicketOwnerUpdate and so the person who sent the email gets
notification when the ticket gets assigned.
Still this is frustrating as heck, as I'm sure you can understand!
Why does
On Fri, Aug 14, 2009 at 9:38 AM, Michiel Beijen wrote:
> I can confirm that it is a bug.. if that helps .. ;-)
>
> http://bugs.otrs.org/show_bug.cgi?id=4149
w00t! Yes, that does help!
If only someone had told me that before wasting 3 or 4 days on it :-)
--
“Don't eat anything you've ever seen
I can confirm that it is a bug.. if that helps .. ;-)
http://bugs.otrs.org/show_bug.cgi?id=4149
Regards,
--
Michiel Beijen
Software Consultant
+31 6 - 457 42 418
Bee Free IT + http://beefreeit.nl
On Wed, Aug 12, 2009 at 18:47, Alan McKay wrote:
> Well, I have a compromise for now. I created
Well, I have a compromise for now. I created a new event for
TicketOwnerUpdate and so the person who sent the email gets
notification when the ticket gets assigned.
Still this is frustrating as heck, as I'm sure you can understand!
Why does everything work except for TicketCreate?
Sounds like a
> I found that the customer user has to be defined in OTRS before any event
> based notifications with Customer as the recipient will fire - both for
> TicketStateUpdate as for TicketCreate events.
Wait a second, this can't be true because my TicketClose email is
triggered on the event "TicketStat
> If you'd set CustomerNotifyJustToRealCustomer in SysConfig to "No", there
> will be nothing in the OTRS log indicating a message has (not) been sent.
> If you'd set CustomerNotifyJustToRealCustomer to "Yes", you'd see a message
> like this in the System Log:
> "Sent no customer notification becau
> I guess this resembles your findings?
Aha! Now I believe we are getting somewhere! In short, I can't do
what I want with EBN.
H. This complicates matters for me. I may have to do this with
"Auto response <--> Queue" instead, if it will not work with EBN
I could say "first time a user
Alan,
I found that the customer user has to be defined in OTRS before any event
based notifications with *Customer* as the recipient will fire - both for
TicketStateUpdate as for TicketCreate events.
If you'd set CustomerNotifyJustToRealCustomer in SysConfig to "No", there
will be nothing in the
On Wed, Aug 12, 2009 at 10:03 AM, LQ Marshall wrote:
> Have you enabled notifications on the user agent's profile preferences?
> - When in doubt print it out.
The user does not have a profile do they?
It's a random customer sending email to our support address.
I go into "users" and then "*" and
Have you enabled notifications on the user agent's profile preferences?
- When in doubt print it out.
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://list
Hey folks,
This is my 3rd attempt at getting some help here - still just largely
getting crickets.
Someone suggested maybe I was not providing enough info. So I
provided the ticket "history" in my previous attempt, and still
crickets.
Is there a link somewhere that tells me what info to send to
11 matches
Mail list logo
