This will impact FB as it moves forward, because FB has custom Differential fields.

@bigo / @frgtn, this probably doesn't cover your use case completely as-is, but I'm not sure how close it gets. In particular, these field types are supported:

• bool, remarkup, text, users
• fully custom fields which reasonably approximate these standard fields

These are not, but support is meaningless because they aren't editable:

• header

These are not, but support is possible:

• date (needs range/comparison conditions, and date value type?)
• int (needs range/comparsion conditions?)
• select (needs custom value type with options)
• credential (unclear what support would look like, needs new value type?)
• fully custom fields which are similar to these standard fields

Basically, do you want to write conditions against any of these unsupported field types at this time? For example, [number of hours] [is greater than] [2], or [some custom select dropdown] [is any of] [custom value 1, custom value 2]? If so, which ones?

Would love to see date fields supported.

The use case I'm trying to cover is to create notifications for open tasks that are past their Due Date (custom date field that we use).

It appears that all the blocking and related tasks have been completed, but this one is still pending. If this is no longer blocked it may be worth re-prioritizing higher and addressing :)

We have a custom field for "Task type" (feature, bug, etc). Would *love* the ability to use herald with this field.

That's supported after D13618.

Only "date", "int" and "credential" remain unsupported.

Thanks for clarifying.