I have added a trigger to a transition in my Workflow to transition issue from To do state to In Progress state once commit is done from Bitbucket as per following instructions https://confluence.atlassian.com/adminjiraserver072/configuring-workflow-triggers-828788041.html, I only added just the first trigger to test if all works well however after commit is done nothing happens to auto transition issue to next state. We are using JIRA Server integrated to Bitbucket Server via application links, commits are done using Github
When I try to troubleshoot to see what went wrong with the trigger, I can't really tell where the problem initiates from because Bitbucket connection shows it's working
We are not connected to FishEye/Crubicle
Another thing which doesn't make sense is that the communication between JIRA and Bitbucket seems to be working well because you can pick up all development events done from Bitbucket to JIRA
I'm not sure what could be wrong, if anyone can point me to the right direction to fix this issue. I've tested few issues and nothing works, at first I added branch created and commit created triggers and thought maybe something is wrong with this setup, I then removed the branch created trigger and left the commit created trigger only as per example above but still not working. When we do a commit we are referencing back to JIRA key in the commit message.
I hope someone can assist with this issue.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot