Send custom payload option missing from Service Management Automation

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Note

This article applies to Jira Service Management 10.4 and earlier. Starting from Jira Service Management 10.5, the feature flag sd.automation.then.webhook.custom.payload.enabled is removed.

The Send custom payload option is missing from the Webhook configuration in Jira Service Management automation rules, as per the screenshot below:

(Auto-migrated image: description temporarily unavailable)

Environment

All the Jira Service Management versions between 4.1.x and 10.4.x. For more information about the feature, see JSD 4.1 release notes.

Diagnosis

The feature flag responsible for enabling this functionality has not been enabled by the application.

Cause

The root cause is not known as of now, due to the very few known cases where this was noticed.

Solution

Enable manually the flag, by following the steps below:

  1. Go to the Dark Features page in your Jira instance by following the instructions available at Enable Dark Feature in Jira

  2. Add the flag below to the Enable Dark Feature box: 

    1. sd.automation.then.webhook.custom.payload.enabled

  3. Try creating a new automation rule and verify that the Send Custom Payload option is available:

(Auto-migrated image: description temporarily unavailable)

Updated on March 21, 2025

Still need help?

The Atlassian Community is here for you.