Trouble triggering Bitbucket REST api via JIRA automation due to IP whitelist issuesIP Whitelisting

[Lim Yi Ying]

I’m trying to trigger a Bitbucket pipeline and create a tag on a commit via web requests using the Bitbucket REST API in Jira automation. Initially, I encountered a 403 error – IP not whitelisted.

After whitelisting the IP range, the issue improved, but I still occasionally hit 403 errors. Because the outgoing IP keeps changing and is unable to be tracked, I can’t reliably identify which IP is causing the failure.

I’ve followed Atlassian’s documentation for whitelisting IPs (IP addresses and domains for Atlassian), but it doesn’t fully solve the issue.

I’m looking for a more reliable solution or best practice for integrating JIRA with Bitbucket in this scenario. Ideally, I’d like a way to trigger pipelines and create tags automatically without constantly chasing changing IPs.

So far, the actions I’ve found available in JIRA developer tools are:

• Create branches
• Create and view pull requests
• View commits
• View builds

…but none seem to allow triggering pipelines or creating tags directly.

Has anyone successfully implemented this type of workflow? Any suggestions for easier, more stable integration between JIRA and Bitbucket would be greatly appreciated.

Thanks in advance for any guidance!

[Lim Yi Ying · Accepted solution]

[Update] Issue solved after whitelisting all IPV6 too. Both IPV4 and IPV6 need to be whitelisted.