Our team has configured Bamboo with JIRA integration working properly. When developers push code changes to our repository, they include ticket references in their commit messages. This creates visible connections between Bamboo builds and the corresponding JIRA issues.
What I’m Trying to Achieve
I want to know if there’s a way to configure Bamboo so it can automatically transition ticket statuses based on build events. Specifically, when a build runs that includes commits referencing certain tickets, I’d like those tickets to automatically move to a “QA Review” status.
Example Scenario
Let’s say a developer commits code with message “Fixed login bug - resolves TICKET-456”. When Bamboo processes this build, I want TICKET-456 to automatically transition from its current state to “QA Review” without manual intervention.
Has anyone successfully implemented this kind of automated workflow integration between these two tools?
We used Bamboo’s built-in JIRA integration instead of writing custom scripts. There’s a ‘JIRA Release’ task that automatically transitions issues when builds pass or fail. Just add it to your build plan’s final stage and tell it which transition to use. You’ll need to set up your JIRA workflow first - make sure the transition exists and Bamboo’s service account can actually run it. We added conditions so it only triggers on successful builds with specific keywords in commit messages. Way less maintenance than webhooks since it’s native Bamboo functionality. Heads up though - bulk transitions will timeout if you’re hitting too many tickets at once, so throttle it if your builds affect dozens of issues.
we use bamboo webhooks for exactly this - works perfectly! set up a webhook that triggers on successful builds, then point it to a simple endpoint. the endpoint parses commit messages and updates jira status through their api. way easier than custom scripts and way less maintenance.
Definitely doable with Bamboo’s REST API and some custom scripting. I built something like this for our team six months ago using Python scripts that run as build plan tasks. Here’s how it works: create a custom script task that scans commit messages for ticket references, then hits JIRA’s REST API to update the status. You’ll need authentication set up between Bamboo and JIRA - either application links or service accounts with the right permissions. Watch out for JIRA’s workflow validation rules though. Some status changes need specific fields filled out or certain conditions met. If your script doesn’t handle this, transitions just fail silently. The parsing part’s pretty simple - just use regex to pull ticket numbers from commit messages. But add some safeguards so you don’t accidentally transition tickets. I’d check the current status first and maybe limit which repos can trigger these auto-updates.