Slow-appearing commits on Jira Server, vs webhooks in new repos

[Nick Wade]

This article, and other community questions like it, refer only to the moment in time when DVCS integration is first established with Jira. 

https://confluence.atlassian.com/jirakb/slow-appearing-commits-from-bitbucket-or-github-in-jira-779160823.html

What about moments in time later on? A new repo, say, server/stuff and a new related Jira project STUFF emerge at the company. A branch commit is made with STUFF-01 pre-pended correctly to the branch. Some time later the branch appears in Jira on the STUFF-01 ticket, perhaps an hour later. Presumably this is the old DVCS connector schedule running.

But webhooks should fire at Jira in the repo and alert Jira that there's a new branch and commit, at least once Jira is aware of this repo. So we try again with STUFF-02 ticket and similarly pre-pended branch name. Same problem, it appears some time later, presumably again on the old schedule. On checking the /stuff repo, no webhooks to Jira are to be found.

Should the DVCS Connector have automatically made necessary webhooks in the new /stuff repo at the time of the first commit appearing and the repo becoming known to Jira? If yes, and it didn't happen, does this mean the OAuth in the repo does not have permissions as per the linked KB? If no, should we do it manually for every new repo?