It used to work till very recently. Is there anything changed in the latest update that we should know about.
Also I've learned that GitHub has rolled out their own add-on "GitHub for Jira" https://marketplace.atlassian.com/apps/1219592/github-for-jira?hosting=cloud&tab=reviews .
Would that cause all the problems that we are seeing with Github/JIRA integration? If so, what is the workaround? As a fyi, the Github for JIRA app is NOT free. - Are there any other FREE apps that we can use to integrate JIRA with Github?
We posted back in November, 2018 that the DVCS Connector for the GitHub.com (Cloud) connection is being decommissioned in favour of new integration mechanism.
We also sent 4-5 emails throughout 2018 and early 2019 to all Jira admins for sites that were using the DVCS Connector. Teams have not been able to create new DVCS Connections to GitHub.com for over 6 months now and we have started to fully disable those few that still have connections, which sounds like what has affected you.
I apologise for this inconvenience but all you have to do is get your Jira and GitHub admin to install the new Connect App: https://marketplace.atlassian.com/apps/1219592/github-for-jira?hosting=cloud&tab=overview.
Should take less than 5 minutes. It will resync all of your data - so no data loss and it will work the same way as before, but much more performant and lots of more improvements coming soon!
Let me know if you are having any trouble connecting to the new app.
@Olga Buslovich The GitHub for Jira app is now owned and maintained by GitHub. So, essentially what you are doing when you install app into your Jira site and you go through the set up flow, it is also installing the GitHub app inside your GitHub account (see https://github.com/marketplace/jira-software-github).
So, if you are referring to the READ access to code, that is actually the GitHub for Jira app (maintained by GitHub), getting access to your code, so it knows how/when to communicate to Jira when there is an commit, branch, or pull request associated with a Jira issue. It then WRITES that data to Jira and is when you see it displayed on the issue detail view, JQL search (https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-developer-reference-967312910.html), and a few other locations where we leverage that development information and improve the Jira experience for you.
Let me know if this is still unclear or a concern for your team, happy to help clarify this further!
@Igor Kosoy Are you still having issues? What's the problem you are seeing?
If you have a lot of Git information, it may take a bit of time to re-sync all of your data - it is back-filling to make sure you don't lose any information as you switch over to the new integration method.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events