I believe this is the issue we saw only after upgraded our JIRA Software to 7.2.4 (from 7.1.9), in LInux:
In any issue detail view, we could see the View Workflow button next to the Status, but clicking on this gave us only a popup screen with the spinning wheel, spinning forever.
We have tested with all browsers and users, including us as admin.
As an admin if we click to edit workflow, then we can see and change the workflow as normal. But we are not able to view the workflow directly from an issue.
Is there anything we should do to fix this?
I'm having the same issue reported by Hung. It used to work, but now it just spins. This is the only thing I see in the log:
2016-12-12 07:41:58,156 http-nio-8080-exec-39 WARN <user> 461x1073015x1 yxocyz <ip>,<ip> /rest/workflowDesigner/latest/workflows [c.a.p.r.c.security.jersey.XsrfResourceFilter] Use of the 'nocheck' value for X-Atlassian-Token has been deprecated since rest 3.0.0. Please use a value of 'no-check' instead.
I'm seeing the same issue in JIRA cloud version. This error shows up when I inspect the page....
Uncaught TypeError: this.html.droppable is not a function at r.init (/s/d41d8cd98f00b204e9800998ecf8427e-T/m40kh0/100024/c/bd54d0ac07f4c86e28581…-opted-out=true&tempo_is_jira_version_equal_or_greater_than_7.0.0=true:472) at r.init (/s/d41d8cd98f00b204e9800998ecf8427e-T/m40kh0/100024/c/bd54d0ac07f4c86e28581…opted-out=true&tempo_is_jira_version_equal_or_greater_than_7.0.0=true:1044) at r.init (batch.js:1404) at r (batch.js:1404) at i._createCanvas (/s/d41d8cd98f00b204e9800998ecf8427e-T/m40kh0/100024/c/bd54d0ac07f4c86e28581…opted-out=true&tempo_is_jira_version_equal_or_greater_than_7.0.0=true:1047) at i.render (/s/d41d8cd98f00b204e9800998ecf8427e-T/m40kh0/100024/c/bd54d0ac07f4c86e28581…opted-out=true&tempo_is_jira_version_equal_or_greater_than_7.0.0=true:1047) at i.onRender (/s/d41d8cd98f00b204e9800998ecf8427e-T/m40kh0/100024/c/bd54d0ac07f4c86e28581…opted-out=true&tempo_is_jira_version_equal_or_greater_than_7.0.0=true:1065) at i.n [as triggerMethod] (/s/d41d8cd98f00b204e9800998ecf8427e-T/m40kh0/100024/c/bd54d0ac07f4c86e28581…t-opted-out=true&tempo_is_jira_version_equal_or_greater_than_7.0.0=true:13) at i.render (/s/d41d8cd98f00b204e9800998ecf8427e-T/m40kh0/100024/c/bd54d0ac07f4c86e28581…t-opted-out=true&tempo_is_jira_version_equal_or_greater_than_7.0.0=true:13) at new u (/s/d41d8cd98f00b204e9800998ecf8427e-T/m40kh0/100024/c/bd54d0ac07f4c86e28581…opted-out=true&tempo_is_jira_version_equal_or_greater_than_7.0.0=true:1068
I have a similar issue after upgrading to 7.5 and found a clearing the cache on your browser fixes the issue. I haven't been able to recreate it and only happens sporadically. I'm also not finding any errors on the logs so not really sure the cause. I've searched for add-on issues but so far no luck on it.
We uninstalled and did not have any problems, but I don't know if your specific plugins would cause problems. It probably would be best if you could create a test environment to test... or confirm with Atlassian support, or plugin vendor support, if uninstalling will really cause problems.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs