GitHub and JIRA not communicating #169147
Replies: 1 comment
-
Step 1 — Check if Jira still sees GitHub commits at all In Jira, open any ticket you’ve recently worked on. Scroll to the “Development” section. See if any GitHub commits, branches, or PRs show up. If nothing shows: the GitHub integration is likely disconnected. If commits show but branches/PRs don’t: it’s a detection/config issue. Step 2 — Try the “commit message” method Make a small commit with the exact Jira ticket key in the commit message, e.g.: css Wait 1–2 minutes and refresh the Jira ticket. If this links: the Jira integration works, but it’s no longer linking from branch names/PR titles — probably due to a rule change. Step 3 — Verify branch name format Ensure branch names are exactly PROJECTKEY-### at the start or right after a slash, e.g.: css Step 4 — Check Jira project settings In Jira Cloud: Go to Project settings → Development tools. Ensure “Development information” is enabled. If there’s a “Branch linking” or “Smart commits” setting, make sure it’s on. Step 5 — Check the GitHub app connection In Jira Cloud: Apps → Manage apps → GitHub for Jira → Check if it says “Connected.” In GitHub: Organization settings → Installed GitHub Apps → GitHub for Jira → Make sure it’s still installed and has access to the right repos. If after this the commit message method works but branch name linking still doesn’t, it’s almost certainly because Atlassian changed the detection rules and you’ll need to add the ticket key to PR descriptions or commit messages instead. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
In our GitHub repository we are putting the JIRA ticket number in the pull request and the title of the branch but it stopped linking them as of a few days ago. Not sure if anyone else is running into this issue. We made no changes to cause the change in flow.
Beta Was this translation helpful? Give feedback.
All reactions