Cascading filters do not have dynamic field history (bug?)

Moderator: crythias

Post Reply
PhyrePhoX
Znuny advanced
Posts: 132
Joined: 05 Dec 2007, 10:56
Znuny Version: 5.0.24 (with ITSM Mo

Cascading filters do not have dynamic field history (bug?)

Post by PhyrePhoX »

Hi,
in order to "debug" my filters, i added a dynamic field "filtername" and in the filter i set this dynamic field to the name of the filter.
So i can see in the tickethistory, which ones of my filters was applied.
This works only for non-cascading filters (stop after match: yes). As soon as more than one filter is applied (stop after match: no), it does not work:
Updated: FieldName=filtername;Value=Filter2;OldValue=;
Only the LAST applied filter is added to the dynamic field and OldValue stays EMPTY.
Is this a bug or am i missing something?
OTRS 5.0.24 (with ITSM Modules) and Znuny 6.4.4 in staging
reneeb
Znuny guru
Posts: 5018
Joined: 13 Mar 2011, 09:54
Znuny Version: 6.0.x
Real Name: Renée Bäcker
Company: Perl-Services.de
Contact:

Re: Cascading filters do not have dynamic field history (bug?)

Post by reneeb »

This is designed behaviour... The postmaster collects all settings in all filter that match and then creates the tickets with those settings. If two settings change the same information, the last one wins.
Perl / Znuny development: http://perl-services.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
PhyrePhoX
Znuny advanced
Posts: 132
Joined: 05 Dec 2007, 10:56
Znuny Version: 5.0.24 (with ITSM Mo

Re: Cascading filters do not have dynamic field history (bug?)

Post by PhyrePhoX »

thanks for the reply. I was kind of hoping that it would be a (fixable) bug and that there would be a workaround somehow.
OTRS 5.0.24 (with ITSM Modules) and Znuny 6.4.4 in staging
Post Reply