Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Automation doesn't see merge commits

Sena Turku Cakmak
Contributor
May 16, 2025

Hello,

I have come across with this issue recently, and I think it was working beforehead. I am using "Build status changed" and "Commit created" triggers for my automations, and none of them are seeing the commits that don't start with ticket number (like ASX-123). I am using Bitbucket, but I cannot detect the merge commits since they start with "Merged" and the ticket name is hidden in branch name (like feature/abc-ASX-123-feature). I want to access the builds and commits regardless of the ticket number being detected, or I am open for workarounds.

Since you already know, merged commits are written automatically by Bitbucket. I don't want to update the commit with a ticket name everytime. I hope there is an alternative way to handle this issue.

Additionally, when I start my automation triggers with a DevOps trigger, for some reason it doesn't see the other DevOps smart values as usable: 2025-05-16 10_31_23-Window.png

As you can see on the attached picture, even my trigger is "Commit Created", the commit smart values are shown to be inside "Other values" , not "Compatible Values". I would like this to be investigated too, if you don't mind.

 

Thank you for your assistance, will be waiting for an answer.

Sena Türkü Cakmak

1 answer

0 votes
John Funk
Community Champion
May 16, 2025

Hi Sena, 

I think you would need to supply a particular issue key for that to work. But you should probably open a support ticket with Atlassian to verify. 

https://support.atlassian.com/contact/#/

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events