GitHub integration with JIRA cloud seems broken ?

[Olga Buslovich]

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

[Taylor · Accepted solution]

@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.

[Igor Kosoy]

Taylor, this is the app we have and it's not responding. Thank you.

[Igor Kosoy]

Never mind, it works after I re-installed it.

[Olga Buslovich]

App works great for us too - Thanks @taylor !!

[Olga Buslovich]

@taylor One quick question regarding GitHub for JIRA app - does it require the READ access to the code ? 

[Taylor]

@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!

[Olga Buslovich]

@Taylor : This is very helpful info. We feel much comfortable with the app now - Thanks a lot!! 

Olga

[Bo Chen]

Hi Taylor, I'm trying to install the app and use it for our project. It doesnt work, we don't see any github development tab. we're using next gen projects

[Edward PikeHD]

I just created a new account and picked the GitHub plugin from the quick setup. When I clicked on it in the "Connect Your Tools" submenu, it could not complete Authentication with GitHub. If there is another GitHub plugin, it should be changed during the project setup wizard. UPDATE: I found this video, it helped. The UI needs more idiot proofing. https://www.youtube.com/watch?v=e5yr7nIqTc8

[Michael Discenza]

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]`

[Michael Discenza]

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]

Same issue here.  Any updates from Atlassian ?

[Taylor]

@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.