Hmm, a filter for what shows would be good enough. I don't really care
what's recorded.
I'm on v3.1 and heard about some history filtering capabilities for v3.2 so
maybe that's why I wasn't able to find this feature?
On Tue, Apr 2, 2013 at 6:05 PM, Gerald Young wrote:
> Sorry, you are looking
Sorry, you are looking at history. I though you were looking at the normal
Ticket Zoom list. History is history. But obviously, if you don't want that
history recorded, you can remove that log from the code.
On Tue, Apr 2, 2013 at 11:04 AM, Gerald Young wrote:
> The filter is for what shows, no
The filter is for what shows, not what's recorded.
On Tue, Apr 2, 2013 at 11:01 AM, Bogdan Iosif wrote:
> Hi,
>
> Can you give a little more info? We may not be talking about the same
> thing.
>
> I looked at Default.pm, Ticket.xml and Framework.xmll and wasn't able to
> find any reference to a
Hi,
Can you give a little more info? We may not be talking about the same thing.
I looked at Default.pm, Ticket.xml and Framework.xmll and wasn't able to
find any reference to a history event filter.
Also, I think I managed to find the code actually dispatching the emails
here
https://github.com
There's a filter in sysconfig
On Tue, Apr 2, 2013 at 4:28 AM, Bogdan Iosif wrote:
> Hi list,
>
> Our agents decided to have informal email notifications dispatched to them
> - configured via Event Notifications - for many types of modifications
> performed upon a ticket. Since we have many agen
Hi list,
Our agents decided to have informal email notifications dispatched to them
- configured via Event Notifications - for many types of modifications
performed upon a ticket. Since we have many agents and many daily
modifications, teach ticket's history looks something like this:
- (some nor
