Issue Summary

This is reproducible on Data Center: (yes)

Webhook URLS for Chat Integrations like slack are converted to the new Automation Secrets. The generated secrets have generic Key names and the key values are hidden from the Jira UI, making future administration of these webhooks unusable. It also makes creating new webhooks very difficult for customers.

Steps to Reproduce

1. Create any Jira with A4J on a version prior to 9.0.1. I used the Jira 9.4 DC Latest LTS templated from Instant Environments to test.
2. Navigate to Jira automation and create a new rule
3. Select Manual trigger
4. Select Send Slack Message for the action.
5. Input a webhook URL e.g http://127.0.0.1/test
6. repeat the above until you have enough rules for your testing
7. Perform the upgrade to A4J 9.0.1 via the manage apps screen.
8. Now when you create a new webhook in version 9.0.1, the webhook URL is replaced with a dropdown that will look similar to the customer's screenshot above.

Expected Results

Webhooks remain identifiable and usable for future admin tasks.

Actual Results

Webhooks are converted to a secret and the drop down list becomes unusable for future admin tasks.

Secrets are also read only in the UI which makes it impossible to change them, they must be recreated and added to the rules again.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.