When opening Visual Studio, it reported "not responding" after the second and subsequent Visual Studio restarts. Now it's fixed.
When an API changes in unexpected ways, applications fail. That was the case with out JIRA extension - when searching for open tasks / issues, JIRA Cloud stopped sending the Status field if not asked for explicitly (which we didn't). This caused a NullReferenceException in upper layers, preventing JIRA extension users from successfully creating branches from JIRA issues.
That's now fixed, of course. Otherwise you wouldn't be reading this!
Remember that you can configure JIRA with gmaster following these instructions: http://blog.gmaster.io/2017/11/configure-jira-with-gmaster.html