Will we ever be able to register a webhook for an addon using the REST API?

Currently you can only register webhooks for issue update/creates with an entry in your atlassian-connect.json file. If we were to do this, our addon would retrieve a webhook post for every issue update/create on every instance our addon is installed in.

This is an immense overhead considering our addon does not store a copy of the issue or work with it on the server. It simply wants to proxy that update/create to the browser via websockets. Moreover, our addon only works with Agile Boards and we only want to know about issues which were created or updated on those agile boards. We’d need to do additional checking to see whether the created/updated issue is on an agile board, figure out which agile board it was in and send the update to browsers viewing that agile board. Non trivial!

It would be great if our app were able to create a new webhook to listen to issue update/creates for issues for the board the user is viewing (via the JQL of the board’s filter) when a user loads the add-on.

To do this I’d need to create a webhook via the REST API. This is not currently possible. Will it ever be?

Thanks!

~Dave

3 Likes

Hi @edave,

This feature request might interest you.

Cheers,
Anne Calantog

1 Like

Hey @edave,

We don’t have a plant to support this in the roadmap in the near term, but I definitely believe that we will support in the long run – so if your question is “Is Atlassian philosophically opposed to adding support for dynamic webhooks?” the answer is “no.”

Dave

1 Like

Thanks for that @acalantog and @dmeyer.

Great to hear that there is nothing security-related preventing this from happening in the future. It’ll be a really powerful feature.

Cheers.

~Dave

1 Like

An initial version of this feature is available: see here for more information.

3 Likes