@jethrokuan This is already existing behavior for dailies, but I didn't realize that it doesn't work with the normal capture templates, so it fixes that. So for example, given the next template:

("pt" "Project note" entry
           "* TODO %?"
           :if-new (file+head+olp "%<%Y%m%d%H%M%S>-${slug}.org" "#+title: ${title}" ("Tasks"))
           :unnarrowed t)

and a similar template for daily, a daily template would properly keep create new TODO entry for existing "Tasks" heading given the same daily date, while in case of the normal capture it would do the next for a new node:

* Tasks
** TODO This is my task

And then running the same template for the same node would yield:

* Tasks
** TODO This is my task
* TODO bar baz

I didn't notice any regression, but just in case would like to pass through your review.

I was a little confused when you said "always trigger :if-new on existing nodes" because it sounds like the opposite of what :if-new is supposed to do, but I tried it out and understand what is meant here. I think for clarity later on we may need to rename/remove the :if-new key.

I was a little confused when you said "always trigger :if-new on existing nodes"
I think for clarity later on we may need to rename/remove the :if-new key.

Oh, I agree with all that. I think #1804 provides perfect opportunity to pull the trigger for the rename. My preference would be s/:if-new/:target, which would be also semantically (given org-capture) correct way to name it.