Supported providers: Bitbucket
Synchronization approach: 2-way
Support for Issue issue branches: yes
On this page:
...
After you’ve added your Bitbucket webhook, changes that are made to the Feature files via IDE, Bitbucket UI or other means, will be uploaded to Jira.
Troubleshooting Git connectivity
Troubleshooting download from Bitbucket
If changes to feature files that are made outside of Jira are not uploading to Jira it may be down to webhook misconfiguration. To verify that your webhook is working as expected you can inspect its request logs to ensure that it gets sent to Jira and that a valid response is received back.
From the Webhooks section of your Repository settings page click on the 'View requests' action link
...
Click on 'Enable History' if it is not already enabled
Make a change to a feature file outside of Jira (e.g. via Bitbucket UI) and then inspect request details by clicking on the ‘View details' link. Note that Jira will send back a successful response with HTTP code 200, even in cases when there are issues downloading from Bitbucket, this is done purposely so that Bitbucket does not trigger the Webhook again and again as it would do in case of error response type.
You can check whether Jira was able to download the feature files by inspecting the message in the response body, like highlighted in example below
In the example above Jira did not download any changes as the project ‘BFJD' is not configured to use issue branches in the App’s Git Integration settings page and the change was made on an issue type branch - 'feature/BFJD-80-demo-issue'
Troubleshooting upload to Bitbucket
If the feature file changes made via Jira are not being uploaded to Bitbucket, you can check the reason from under the History tab on the issue page like shown below
...
In this case our project was configured to use issues branches in the App’s Git Integration settings page however no branch for this issue could be found at the time of the change