Condition for Article.Sender don't seem to work correctly*

Technical assistance
#1

Infos:

  • Used Zammad version: 3.4.x
  • Used Zammad installation source: source
  • Operating system: Debian 10
  • Browser + version: any

Expected behavior:

  • Condition for ‘Sender’ within trigger/scheduler should work

Actual behavior:

  • Scheduler job condition Sender != System doesn’t work
  • Latest article sender ID (within DB) sender_id: 3

Steps to reproduce the behavior:

  • Have ‘System’ send a notification (e.g. via e-mail) to the customer
  • Create scheduler job with condition: Sender != System
#2

*) or maybe I got it wrong: Reading though some community posts, I’m not 100% sure if the conditions for ‘article’ refer to only the latest article (which I thought), or ALL of them. Could someone clarify? :slight_smile:

#3

Please provide your complete trigger configuration.
Fishing in the dark doesn’t help us both. :wink:

#4

After a bit more of testing, it seems that my guess, that the ‘article’ condition takes a look at all articles instead of (what I initially thought) only the last article, was right. Could you confirm this?

For sake of completeness, here’s my Scheduler conditions—but it sure wouldn’t work if Sender looks at all articles.

Bildschirmfoto 2020-06-19 um 10.44.49
Bildschirmfoto 2020-06-19 um 10.44.491430×880 60.3 KB

#5

The sender condition is not at fault, I removed it in a test ticket on my end and tried again. Nothing happens.

#6

Quick update: It seems, scheduler can’t check for articles (yet). I’ll open an issue on GitHub.

#7

And there you go:

#8

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.