Datetime object and Triggers

[AidanA]

• Used Zammad version: 6.0
• Used Zammad installation type: package
• Operating system: Ubuntu Server
• Browser + version: All

Expected behavior:

• Creating a datetime ticket oject to be used for granular control seperate from the pending till field react the same with triggers

Actual behavior:

• Pending till when used in a trigger with the relative condition places a Date and Time at the specified interval. A custom datetime object does not.

Steps to reproduce the behavior:

Create custom Ticket Object type:datetime, Allow future: yes, Allow Past:no

Create custom ‘Progress’ field (options:Meeting Convened,Proffered,Legal)

Create individual triggers to automatically set custom datetime object 2 months in the future based on
the custom progress field changing.

[AidanA]

I did further testing. After removing the group condition, it still did not work. I put the group condition back in updated to 6.1 and it still would not work. I moved the group condition below the other conditions and it worked. It seems to be that if the group condition is the first in the tree the trigger fails, but works in any other configuration.

[MrGeneration]

I’m unable to reproduce that on 6.1.0.876840eb8.

My slightly different test trigger correctly sets my datetime objects to a new value

Are you sure your conditions are met?

[AidanA]

They were met according to my understanding of the logic system the triggers follow in the pcitures above. If I put the group back to its original location (first AND operator) it causes the trigger not to run. If I put Ticket Progress then Group, the trigger actions properly. I’m on the latest stable still as of last night (updated entire ubuntu server host and all packages). I’m betting it is something I have edited, but the only file I manually update is attachments.jst.eco to enable an HTML5 audio player for WAV and MP3 attachments (see my other posts).