Bug while clicking on wokflow-buttons (or show workflow link) in a displayed

[Mark Ariu]

Hello Jira-Support,

I'm in the detailled overview of a manually created filter and I have one ticket is selected. The I try to click on a workflow-button (or on the link "show workflow"). Then I see the loading circle and nothing happens further. I have Jira Software version 7.11.1.

In the browser-console of firefox (newest version) I got the following errors:

Downloading resources: js!/s/00c5644b903c791d4ab2a417b6b48d7e-T/wdxgqr/711001/b6b48b2829824b869586ac216d119363/4466dabd677e3f349638a22db7d43617/_/download/contextbatch/js/jira.edit.issue,-_super,-jira.view.issue,-atl.general,-jira.general,-jira.rich.editor,-jira.navigator.kickass,-com.atlassian.jira.plugins.jira-development-integration-plugin:7,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-viewissue.standalone,-jira.navigator.advanced,-jira.navigator.simple/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=de-DE&nps-acknowledged=true&nps-not-opted-out=true&richediton=true&spectrum=true&whisper-enabled=true!order batch.js:436:165

Laden fehlgeschlagen für das <script> mit der Quelle "http://jira.acb.de/s/00c5644b903c791d4ab2a417b6b48d7e-T/wdxgqr/711001/b6b48b2829824b869586ac216d119363/4466dabd677e3f349638a22db7d43617/_/download/contextbatch/js/jira.edit.issue,-_super,-jira.view.issue,-atl.general,-jira.general,-jira.rich.editor,-jira.navigator.kickass,-com.atlassian.jira.plugins.jira-development-integration-plugin:7,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-viewissue.standalone,-jira.navigator.advanced,-jira.navigator.simple/batch.js?agile_global_adm...". JUNG-15:1

Downloading resources: css!/s/ef94573d419b9efaa99e2c6e983a16a5-T/wdxgqr/711001/b6b48b2829824b869586ac216d119363/192449a22fd18e800b005f40939ce162/_/download/contextbatch/css/com.atlassian.jira.plugins.jira-workflow-designer.workflow-designer,-_super,-com.atlassian.jira.plugins.jira-development-integration-plugin:7,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-jira.view.issue,-jira.edit.issue,-jira.navigator.kickass,-atl.general,-viewissue.standalone/batch.css?agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira.create.linked.issue=true&nps-acknowledged=true&nps-not-opted-out=true&richediton=true&spectrum=true&whisper-enabled=true js!/s/1081d43add84603ac926e1bd686a3a68-T/wdxgqr/711001/b6b48b2829824b869586ac216d119363/192449a22fd18e800b005f40939ce162/_/download/contextbatch/js/com.atlassian.jira.plugins.jira-workflow-designer.workflow-designer,-_super,-com.atlassian.jira.plugins.jira-development-integration-plugin:7,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-jira.view.issue,-jira.edit.issue,-jira.navigator.kickass,-atl.general,-viewissue.standalone/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=de-DE&nps-acknowledged=true&nps-not-opted-out=true&richediton=true&spectrum=true&whisper-enabled=true!order batch.js:436:165

TypeError: B is undefined[Weitere Informationen] batch.js:4552:848 Laden fehlgeschlagen für das <script> mit der Quelle "http://jira.acb.de/s/1081d43add84603ac926e1bd686a3a68-T/wdxgqr/711001/b6b48b2829824b869586ac216d119363/192449a22fd18e800b005f40939ce162/_/download/contextbatch/js/com.atlassian.jira.plugins.jira-workflow-designer.workflow-designer,-_super,-com.atlassian.jira.plugins.jira-development-integration-plugin:7,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-jira.view.issue,-jira.edit.issue,-jira.navigator.kickass,-atl.general,-viewissue.standalone/batch.js?agile_global_admin_conditio...". JUNG-15:1

Source-Map-Fehler: request failed with status 404 Ressourcen-Adresse: http://jira.acb.de/s/56cde068339ba3833b71df9692b83980-T/wdxgqr/711001/b6b48b2829824b869586ac216d119363/c8a8c9298e20c2895e6414c012fe4418/_/download/contextbatch/js/com.atlassian.jira.plugins.jira-development-integration-plugin:7,-_super,-jira.view.issue,-jira.navigator.kickass,-atl.general,-viewissue.standalone/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira.create.linked.iss... Source-Map-Adresse: 7.0ce9e40d2820bfa71df7.js.map;[Weitere Informationen]

When I'm directly on a ticket (not whitin a filterview) then evenrything works.

Many thanks,

Mark

[Andy Heinzer · Accepted solution]

Hi Mark,

It sounds like you might be encountering a problem similar to that described in JIRA elements fail to render with HTTP 400 error

In that KB it explains that this problem is caused by the use of a Windows based proxy in front of Jira.  I am not sure if you are using a proxy with Jira from this information yet, or if it happens to be on a windows machine.   If you are, then it's probably worth trying to follow those steps to correct this.

If you are not, then I would still be interested to see if you can instead follow the steps in How to bypass a Proxy and SSL to test network connectivity.   It is still possible that the problem you see here could be caused by a proxy/firewall/load balancer that handles traffic in front of Jira.  These steps will have you create a new connector for Jira to use in order to access the site without having to force traffic through this other address.  This way, if you can access the server directly, you can then use an address such as localhost:8081 in order to try to access the Jira site.  I am interested to see if you can recreate this problem when using that address instead.  If not, it tends to indicate that the problem is with the proxy or the way Jira is configured to use that proxy.

Please let us know the results.

Andy

[Mark Ariu]

Many Thanks Andrew,

Problem solved.

[Mark Ariu]

I tested a little more and found out, that the bug only comes up when I'm in a self created filter.