USM Content
Jira webhooks
As of November 15, 2023, we've upgraded the webhook scheme of the Smartsheet Jira Connector for enhanced efficiency. All bi-directional workflows created after this date will benefit from a shared webhook system. This strategic enhancement is designed to align with the July 2024 Atlassian Jira Cloud limit change to 100 Jira webhooks per Jira environment, which introduced a limit of 100 Jira Webhooks per Jira Cloud environment. The advantage? You're now equipped to establish as many workflows as necessary, circumventing Jira's webhook constraints.
Convert existing workflows to the new model
With the recent update to Atlassian's Jira webhook limit in July 2024, it's now recommended that you migrate all your workflows to the new shared webhook model. To start this process, a System Admin or Jira Connector Admin from your account must do the following:
- Navigate to the Jira Connector Admin Dashboard.
Select the Migrate Workflows button.
If you receive an alert indicating that some workflows failed to migrate after selecting the button, you should try again. Once all workflows have been successfully migrated, the Migrate Workflows button will no longer be visible. Note that this change won't impact existing workflows, and there's no need to re-enable them.
Consolidate automated workflows when possible
Atlassian’s best practices for webhooks suggest having as few webhooks as possible. One way to consolidate workflows is to use a more general filter on the workflow and use the connected sheet as a staging site for your data. You can then use DataMesh to filter and send data between sheets.
If you have many workflows and are experiencing Jira slowness, visit Atlassian’s webhook troubleshooting guide to find ways your Jira Admin can diagnose which webhooks could be causing the slowness.
Enable asynchronous webhook processing
By default, Jira Server and DataCenter process these webhooks individually after every change to an issue.
Jira has an unofficial dark feature tells Jira to process webhooks asynchronously, making the UI more responsive after changes. Enabling this change will require permission from a user with Jira Administrator.
According to this Jira ticket, you can enable the feature by:
- Manually enable the com.atlassian.jira.webhookEventsAsyncProcessing feature flag with the following instructions.
- Restart your Jira instance (or each node in case of DC)
The following versions of Jira Server and DataCenter can enable this feature:
- 8.13.25, 8.20.12 or later
- 9.2.0 or later
FAQ
Webhook limit exceeded
If you've received this message, this means you're using more than 100 webhooks within your Jira environment. As Atlassian is enforcing a 100 webhook limit per Jira Cloud instance, you should take the following actions to reduce your webhook count below 100.
- Identify how many bi-directional workflows you're using,
- Disable enough bi-directional workflows to drop below the 100 webhook count (i.e. will need to have at minimum less than 100 bi-directional workflows).
- Once the bi-directional workflows are disabled by an admin or the workflow owner, you can convert existing workflows to the new system.
- Have the workflow owner refresh the page, then select the Reset button to re-enable the workflow. After confirming the workflow has successfully reset, continue this process for the remaining disabled bi-directional Jira workflows.
This action should be taken by the workflow owner as any Jira user can disable a workflow but only the owner can re-enable a workflow.