Thanks for the answer, I will try my luck with the generic agent / notification…
- Swen
On May 31, 2014, at 3:55 AM, Michiel Beijen wrote:
> Hi Swen,
>
> You're right, there's no support for variables in the Bulk Action
> email. I know, I implemented it, and this was not a requirement. :D
>
>
Hi Swen,
You're right, there's no support for variables in the Bulk Action
email. I know, I implemented it, and this was not a requirement. :D
If you can't do coding, I think the best solution would be a
combination of the two actions Gerald suggested: Create a
"Notification (Event Based) which c
Thanks,
I tried both variables in the subject but they don’t translate correctly
(Screenshot: http://o7.no/1pEMihD) . It seems that OTRS is not evaluating for a
variable in the subject field for bulk actions. :(
- Swen
On May 30, 2014, at 1:14 PM, Gerald Young wrote:
> I'd think about a Gene
I'd think about a Generic Agent/Notification Event combination.
(?) (?) might be options in
either your bulk case or Notification Event
On Fri, May 30, 2014 at 1:58 PM, NetSaint wrote:
> Hello,
>
> I am working for an ISP. I use a queue within OTRS for the abuse helpdesk
> address.
>
> Recent
Hello,
I am working for an ISP. I use a queue within OTRS for the abuse helpdesk
address.
Recently, I got over 500 tickets over the weekend into my queue, which is
unusual. Some copyright company decided to notify for each mp3 song a user
downloaded. So, these 500 tickets belong to just 5 user
