Do Notifications on Task table fire on extended tables?

[The SN Nerd]

I've noticed that when I set 'Table' to 'Task' on any given notification, it is never fired when triggering from a table that

Even the OOB notification "Task approved" is not firing (tested on an Incident record, OOB).

As soon as I change the notification to use the Incident table, sending to the Assigned to field, it works.

Yes, the user has an email record, the user is not me, and send to even creator is checked. It works if the table is set to Incident.

This seems inconsistent with the way the rest of the tool works. Also, why do they provided OOB notifications if they don't even fire?

I've testing on an OOB Fuji system and a customized Eureka system. The issue occurs in both systems.

Aren't Notifications on Task table supposed fire on extended tables? Why not?

[peterraeves]

I encountered this issue again. This behaviour is really bad 😕 I wonder why they did not just add the 'extended' checkbox, like they have on ui policies and stuff, where you can choose whether you want to run it on extended tables or not...

[The SN Nerd]

This is particularly annoying for Case Types!