Jira Automations - Webhooks reset after export/import - impacting Sandbox refreshese

[Paul Madison]

With the recent changes to Incoming Webhooks, we are getting new webhook urls when when we import our automations after refreshing our Sandbox.  This is a huge pain because we have to reconfigure dozens of automation actions across many automations.  We refresh our Sandbox multiple times a year for testing purposes and this will be a great pain for us.  Atlassian support didn't provide any help, so I am asking here.

Is anyone else experiencing this issue?  How are you working around it/dealing with it?

[Paul Madison]

Atlassian has opened a feature request to preserve automations when refreshing a Sandbox.

https://jira.atlassian.com/browse/CLOUD-12564

[Marc - Devoteam]

Hi @Paul Madison 

Nice, I will follow this.

[Rick Westbrock]

Unfortunately that does mean that if you have modified an automation rule with a webhook trigger in production you will have to manually update the rule in sandbox to match but that's certainly easier than modifying multiple external systems with the new webhook URL.

[Paul Madison]

That's not helpful when all my automations get wiped out in a refresh and I have to import them again and reconfigure dozens of them.

Webhooks are no longer preserved on an export, which is going to be painful for us.

[Marc - Devoteam]

HI @Paul Madison 

I can't say I have a fix for this issue.

I did ask your question on the topic that published on this change, see Update-on-Incoming-Webhooks-Trigger-for-Atlassian-Automation