Answer
This is confirmed, intentional behavior rather than a bug — the notification logic treats a task as something that needs surfacing to the assignee specifically because someone else created it for them; a self-assigned task assumes you're already aware of it since you created it, so it deliberately doesn't generate the same notification-panel entry.