Issue Summary

When users need to use Webhooks, for example in automation, and the allow listing polices are enabled, the Atlassian IP's are automatically blocked and in order to be accessible they need to be added in the allowlist which uses 32 out of the available 100 -> 500 configurable IPs.

Steps to Reproduce

1. Enable allow listing policies
2. Attempt to use a webhook from an automation rule pointing to the originating instance.
3. Unless the Atlassian IPs are added in the allowlisting policies the webhok operation fails.

Expected Results

Atlassian's own IPs should be allowed automatically even if the allowlisting policies are turned on. Also this shouldn't count toward the 100 limit provided to the customers

Actual Results

Atlassian IPs need to be manually added and they count towards the 100 -> 500 IP limit.

jira { "errorMessages": [ "The IP address has been rejected because it is not on the allowedlist. See your admin for more information." ], "errors": {} }

Workaround

Customer needs to manually add Atlassian's IPs in the allowlist.