Development Panel missing and Workflow triggers not working
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
The Development Panel is not appearing when viewing an Issue in Jira
The Source tab appears on Jira View Issue page instead
Workflow triggers are not working. For example you'll get the response "Jira is unable to communicate with Stash" when attempting to add a Workflow Trigger in JIRA.
The following appears in the atlassian-jira.log with additional DEBUG logging (see the Diagnosis section below for more details):
Case1:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
2015-01-21 15:53:26,681 NavLink RestCapabilitiesClient:thread-1 DEBUG anonymous [menu.client.capabilities.RestCapabilitiesClient] Stacktrace:
javax.net.ssl.SSLException: hostname in certificate didn't match: <*.atlassian.com> != <unknown>
at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:227)
at org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54)
at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:147)
at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:437)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:644)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1138)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1076)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1050)
at com.atlassian.plugins.navlink.consumer.http.HttpRequest.executeRequest(HttpRequest.java:26)
at com.atlassian.plugins.navlink.consumer.http.HttpRequestFactoryImpl.executeGetRequest(HttpRequestFactoryImpl.java:65)
at com.atlassian.plugins.navlink.consumer.menu.client.capabilities.RestCapabilitiesClient.submitRequest(RestCapabilitiesClient.java:78)
at com.atlassian.plugins.navlink.consumer.menu.client.capabilities.RestCapabilitiesClient$1.call(RestCapabilitiesClient.java:63)
at com.atlassian.plugins.navlink.consumer.menu.client.capabilities.RestCapabilitiesClient$1.call(RestCapabilitiesClient.java:56)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)or
Case2:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
2015-11-25 11:12:28,833 NavLink RestCapabilitiesClient:thread-1 DEBUG anonymous [menu.client.capabilities.RestCapabilitiesClient] Stacktrace:
javax.net.ssl.SSLException: Received fatal alert: protocol_version
at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)
at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:2023)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1125)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)Diagnosis
Application Link between Jira and Stash is SSL encrypted.
Enabling DEBUG logging for the following packages reveal that there is a mismatch in hostname and the FQDN in SSL certificate(at this time the logging level for these packages do not show the errors by default):
com.atlassian.plugins.navlink.consumer.menu.client.capabilities.RestCapabilitiesClientcom.atlassian.applinks.core.auth.ApplicationLinkRequestFactoryFactoryImplcom.atlassian.plugins.navlink.consumer.menu.services.CachingRemoteNavigationLinkServiceImpl
Once DEBUG logging is enabled there are multiple ways we can trigger Jira to send a request for the capabilities to Stash:
Attempting to add a Workflow Trigger should send the capabilities request
Viewing the Development Tools page in Jira when managing a project and clicking 'Refresh' should send the capabilities request
ℹ️ See how to Change logging levels in Jira Data Center
Cause
During communication between Jira and Stash, Jira will send a request to confirm Stash is capable of handling Workflow Triggers and displaying the Development Panel.
Case1: The link is not working because the hostname does not match the FQDN(Fully Qualified Domain Name) configured in the SSL certificate.
Case2: The link is not working because the remote Host can't accept TLS/SSL version requested by Jira. Eg. remote host supports TLSv1 only, Jira asks TLSv1.2.
Resolution
Case1: Ensure the FQDN(Fully Qualified Domain Name) in SSL certificate matches Jira and Stash hostnames.
Case2: Configure environment settings something like -Dhttps.protocols=TLSv1 -Djdk.tls.client.protocols=TLSv1, see also JSWSERVER-14914 - NavLink RestCapabilitiesClient ignoring system properties.
Was this helpful?