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?
Please advise.
Thanks, Olga
@Olga Buslovich and @Igor Kosoy Hey, hopefully I can help you out here.
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.
https://www.atlassian.com/blog/jira-software/github-for-jira?_ga=2.159498621.1989764802.1578878289-2096290785.1531959152
https://community.atlassian.com/t5/Jira-articles/Everything-you-need-to-know-about-migrating-from-the-DVCS/ba-p/945910
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.
Same issue here. Any updates from Atlassian ?
Taylor, this is the app we have and it's not responding. Thank you.
Never mind, it works after I re-installed it.
App works great for us too - Thanks @taylor !!
Also, note that the new connector requires you to put your issue ids in brackets to be parsed and associated properly to issues.
Before, `ID-231` would work, now you have to do `[ID-231]`
Actually, nevermind, this is incorrect. You don't need brackets -- it just took forever to scan our commit history and the latest commit was associated quickly after the backlog was scanned!
@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.
It looks like you're new here. Sign in or register to get started.
