hey, try setting up a jira webhook that triggers a small automation script. i got it working by calling bitbucket’s api directly when the issue moves status. works pretty well for me, might need a bit of tweaking.
I approached a similar need by developing a custom integration that listens for specific webhook events from JIRA and then invokes a script to update files in the repository. My system monitors changes and filters for target statuses before appending formatted ticket information into a log file. This method allowed for the incorporation of additional data such as timestamps and user details. Although it required some trial and error during the development phase, the end result streamlined operations and reduced manual updating, proving to be both reliable and efficient in a production environment.