Forums

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

Associating deployments with Jira issues (github integration)

Nikola Pavlovic
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!
June 6, 2023

Hello.

At https://support.atlassian.com/jira-cloud-administration/docs/use-the-github-for-jira-app/#View-GitHub-information-in-Jira-issues, it is clearly stated 

Deployments are linked to Jira issues by scanning for Jira issue keys in all commit messages on the deployed branch since the last successful deployment. 

and otherwise visually presented Associating_Deployments_with_Jira_Issues_.png

that deployment #7 will be associated with all issues found in commit messages since the last successful deployment.

This doesn't appear to be the case for us. The only deployments/builds that get associated with a jira issue are the ones triggered by pull requests that contain commits that mention the specific jira issue id. So in terms of the above flow, Deployment #7 would be associated with JIRA-1, JIRA-10, JIRA-11 and JIRA-2 would still stay associated with the previous, failed build, even though since the branch in question (main) was obviously successfully built by deployment #7, and with it the changes/code related to JIRA-2, making it successfully deployed.

What am I missing? How do I solve this?

0 answers

Suggest an answer

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

Atlassian Community Events