Issue

• The DevOptics integration with Jira Server no longer works with Chrome versions higher to 85 and the latest Safari version. As of Chrome 85, released on August 25th 2020, there is a new security feature enabled by default in the browser, which changes the way that the browser handles 3rd party cookies. See here for more details on the feature. This change in the default cookie behaviour is preventing the DevOptics integration with Jira Server from working.
• You see a warning message in Jira when installing the CloudBees Devoptics plugin, indicating that it is incompatible or an update is required.

Environment

• CloudBees CI (CloudBees Core)
• CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
• CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
• CloudBees CI (CloudBees Core) on traditional platforms - Client controller
• CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
• CloudBees Jenkins Enterprise
• CloudBees Jenkins Enterprise - Managed controller
• CloudBees Jenkins Enterprise - Operations Center
• CloudBees Jenkins Platform - Client controller
• CloudBees Jenkins Platform - Operations Center
• CloudBees Jenkins Distribution
• Chrome browser - 85
• Safari browser - 14

Related Issue(s)

• JRASERVER-70471

Summary

The core features of DevOptics Value Streams are unaffected. Also, customers using the Jira Cloud integration or the “Jenkins master as a Jira proxy” integration will be unaffected. What an affected customer will see is that they no longer have Jira ticket details available in the Value Streams UI.

Anyone using the Jira Server integration and is using a Chrome version higher than 85 will be impacted. This issue is nothing to do with the version of Jira Server being used. You may have a working integration right now, then simply update their Chrome browser to the latest, and then no longer have a working integration.

Workaround

There is a ticket open with Atlassian (https://jira.atlassian.com/browse/JRASERVER-70471) requesting that they implement a fix, but that is unlikely to happen any time soon.

Workarounds for now include:
* Use Firefox, though it is unclear if/when they will follow Chrome and change their default cookie behaviour to match.
* Use the “Jenkins master as a Jira proxy” integration.
* Disable the cookie behaviour in Chrome: chrome://flags -> “SameSite by default cookies” -> Disabled.
* Disable the cookie behaviour in Safari: Preferences -> Privacy -> uncheck “Prevent cross-site tracking”.
* Adding cookie headers at a Tomcat level may also help with this issue.
* Additionally, adding cookie headers at a proxy level may also work.

Incompatibility resolution

Additionally, if you get a warning message in Jira when installing the CloudBees Devoptics plugin, indicating that it is incompatible or an update is required, you may need to contact the CloudBees Support by raising a support ticket, so the Devoptics Team can review its compatibility with your Jira Server version, and update the list of compatible version so the warning is no longer shown.