Hi there!
We are evaluating the pros/cons of leveraging Atlassian's Github -> Jira integration app. I have searched everywhere and can not find any examples of a PR being referenced in Jira comments, but I could've sworn I've seen it somewhere and it looked similar to the Teams integration (see screenshot).
Can anyone help provide a screenshot or confirm whether or not this functionality even exists?
What other features of the Github Integration are really useful to your teams?
Thanks!
Hi @sweber
You're right to double-check—Atlassian’s native GitHub → Jira integration does not currently support automatically adding PR references into Jira comments the way the Teams integration does.
What it does offer is smart linking: if your PRs mention a Jira issue key in the title or description, Jira will show that link in the issue under the "Development" panel.
However, this doesn’t post any updates directly into the issue’s comment stream, which can be a gap if your teams rely on visible, threaded updates for reviews or approvals.
That said, if you need a truly complete context sync—like referencing PRs in comments, syncing labels, custom fields, or linking across multiple repos or Jira projects—you might want to explore OpsHub Integration Manager (you can start for absolutely free).
It supports richer, bi-directional sync with full traceability between GitHub and Jira (including in-line images, comments, metadata, and more). Hope this helps! Happy to share a setup screenshot if you’d like.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk What does that look like in practice though? Is it just text and a link or does it have formatting that updates? For example with that Teams integration I have screenshotted in OP it will update to 'Merged' once the PR is merged. I thought the Github integration for Jira did something similar?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you wanting to auto transition to a particular status when the PR is merged? If so, you can create an automation rule like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk While that is useful, no. Not looking for anything to do with automation at this point in time.
Just want to know if the Jira + GitHub integration has a similar feature to the one in MSFT Teams that I screenshotted in OP. If so, hoping to see a screenshot
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk In the comments section of a Jira Issue. Like if someone were to paste a link a PR in a comment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, so you would create an automation rule like above except that you are going to add a Comment instead of transitioning the issue. Then see this article for the smart values for the various pull request related components.
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.