Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
6.3.8, 6.3.9
-
6.03
-
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Behavior
After migrating from JIRA OnDemand to JIRA v6.3.8, trying to view/edit certain workflows in Diagram mode leads to a server error in the GUI.
The following stack is found in catalina.out:
/rest/workflowDesigner/latest/workflows [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: No initial status java.lang.IllegalArgumentException: No initial status at com.atlassian.jira.plugins.workflowdesigner.layout.LayoutUpdaterImpl$Updater.getInitialStepId(LayoutUpdaterImpl.java:347) at com.atlassian.jira.plugins.workflowdesigner.layout.LayoutUpdaterImpl$Updater.addedTransitions(LayoutUpdaterImpl.java:287) at com.atlassian.jira.plugins.workflowdesigner.layout.LayoutUpdaterImpl$Updater.update(LayoutUpdaterImpl.java:72) at com.atlassian.jira.plugins.workflowdesigner.layout.LayoutUpdaterImpl.updateLayoutWithDataFromWorkflow(LayoutUpdaterImpl.java:48) at com.sysbliss.jira.plugins.workflow.manager.WorkflowLayoutManagerImpl.updateLayoutWithDataFromWorkflow(WorkflowLayoutManagerImpl.java:164) at com.sysbliss.jira.plugins.workflow.manager.WorkflowLayoutManagerImpl.updateExistingLayout(WorkflowLayoutManagerImpl.java:142) at com.sysbliss.jira.plugins.workflow.manager.WorkflowLayoutManagerImpl.getExistingLayoutOrCreate(WorkflowLayoutManagerImpl.java:79) at com.atlassian.jira.plugins.workflowdesigner.layout.WorkflowLayoutsImpl.getLayout(WorkflowLayoutsImpl.java:101) at com.atlassian.jira.plugins.workflowdesigner.rest.WorkflowsResource.getWorkflow(WorkflowsResource.java:69) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:100) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept(ExpandInterceptor.java:38) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.invokeMethodWithInterceptors(DispatchProviderHelper.java:132) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker._dispatch(DispatchProviderHelper.java:230) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
This issue was reproduced locally using a customer XML backup.
Steps to Reproduce
- Migrate from JIRA OnDemand to JIRA v6.3.8 Server
- Try to view/edit workflows as Diagram
Workaround
- Export problematic workflow as XML
- Import the same XML back into JIRA
- Navigate to Administration >> Issues >> Workflow Schemes to re-assign issue types to imported workflow
When utilizing this workaround, the only changes that are occurring to the workflow itself are the author and creation date - this can be verified by comparing XML exports of the same workflow pre- and post-import - but the imported workflow is available to view/edit as a diagram at Administration >> Issues >> Workflows.
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-