Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Why does Jira Automation *PR merged* only detect task IDs in title but not in nested commit messages

Why does Jira Automation *PR merged* only detect task IDs in title but not in nested commit messages

Haitham Josef Elfaham
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 12, 2026


When I create a merge request from a feature branch where the underlying commit contains a task ID (see screenshot: LPBIT-3036 is the task ID in jira), it does not get detected by the automation, keeping in mind that the MR title is UAT (since we are merging UAT environment to Prod environment). The automation only gets triggered if the title contains the id, i.e., if instead of UAT it has LPBIT-3036  then it would work. The expectation here is to detect in a recursive manner all commit message and their contained ID so it can invoke the action accordingly. Keep in mind this used to work until Screenshot 2026-05-12 at 16.52.26.png end of March 2026.Screenshot 2026-05-12 at 16.45.21.png

0 answers

Suggest an answer

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

Atlassian Community Events