How to Resolve Webhook URL Addition Issues in Jira Data Center 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
The Webhook URL field is now a dropdown, while it used to be a field where a URL could be directly added. Users are unable to add more options to the Webhook URL field.
Environment
Automation for Jira 9.x, 10.x
Solution
This behavior is expected, as explained in the documentation - Create and edit masked secret keys for automation rules.
Automation for Jira 9 introduced a new way to store confidential data, such as authorization tokens for webhook URLs:
Instead of being shown in plain text in the automation rules, such data is now stored in the Jira Database.
To add new Webhook URLs (or tokens), follow the steps below:
Go to ⚙ > System > Automation rules, and then go to ... > Manage secret keys
Create a new Key by choosing the Key Name of your choice (for example: "Slack Webhook URL A") and saving the URL in the Key Value field
Once the new key is created, this Key will be shown in the Webhook URLs dropdown menu of the Send Slack Message action
Was this helpful?