Jira Bridge using SG Webhooks

I’m curious if anyone has gotten the Jira to SG bridge working with SG Webhooks instead of the SG event daemon? The SG event daemon is deprecated, doesn’t always captures all the event changes in SG and is difficult to manage and monitor. Seems like Webhooks would make it more streamlined.

Anyone been able to get this to work and have any tips to implement it?

Cheers,
Scott

It’s not deprecated?

I would also argue that the Daemon allows you to replay events while webhooks, if missed, are missed.

1 Like

While it may not be deprecated on the Github repo the SG team told me years ago that it was. My own experience with it backed up what they told me, which is that the event daemon can regularly miss events that happen in SG and is hard to manage.

I do agree that its nice to be able to re-run past events that happened in SG. I wish the Webhooks offered that ability. However, you can write your webhook code to query and feed in previous events for manually processing.

I’ve embraced Webhooks and find them much easier to work with and reliable. My $.02 :slight_smile:

There are a few new developers on the Sg team and the event daemon has been updated recently.

Other than that, I don’t have info on wheter anyone uses webhooks for the Jira bridge, everyone I know runs it from events, wheter the official daemon or derivatives of it. :slight_smile:

Thanks for the link and pointing that out. Apparently, my info is outdated. I wonder if they fixed those core issues about missed events. I reached out to SG support and they have have a feature request for the Jira bridge to use Webhooks but they haven’t done anything with it.

I might do a little investigating to see what it would take to support Webhooks instead since our event automation will use Webhooks, seem silly to only run the event daemon for the Jira bridge.

Thanks again!

1 Like