Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
6.2, 6.4.0.3, 6.7.11
-
None
-
6.02
-
8
-
Severity 3 - Minor
-
0
-
Description
Summary
JIRA Agile has a simplify workflow button, which puts the workflow into a special state that Agile expects it to be. Admins can modify the workflow through JIRA, which will put it into a state that means Agile can no longer use it. However, Agile can still offer to simplify the workflow. This can result in confusion and also generates errors when trying to simplify it.
Steps to Reproduce
- Create a project. Eg: TEST
- Create multiple issues in project TEST
- Create a board for this project and then change the workflow to Simplified Workflow Scheme in Agile
- Edit the workflow "Simplified Workflow Scheme" for project TEST.
- Edit the Draft and publish it. Eg: add new statuses and transition then, it appear as if the project TEST is not using Simplified Workflow Scheme in Agile
- Go to the board again.
- Click on the Simplified Workflow.
Expected Results
The workflow can be simplified, or it lists 'Agile Simplified Workflow unavailable'.
Actual Results
It will hang and throw the following error:
2015-06-26 03:55:52,035 http-bio-8080-exec-24922 ERROR jirasupport 235x11196994x1 1jkdqme 10.125.72.11,127.0.0.1 /rest/greenhopper/1.0/workflow/convert.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: The workflow is assigned to workflow schemes com.atlassian.jira.workflow.WorkflowException: The workflow is assigned to workflow schemes at com.atlassian.jira.workflow.OSWorkflowManager.deleteWorkflow(OSWorkflowManager.java:495) at sun.reflect.GeneratedMethodAccessor13492.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129) at com.sun.proxy.$Proxy385.deleteWorkflow(Unknown Source) <+2> (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154) at com.sun.proxy.$Proxy385.deleteWorkflow(Unknown Source) at com.atlassian.greenhopper.service.workflow.WorkflowServiceImpl.deleteWorkflow(WorkflowServiceImpl.java:312) at com.atlassian.greenhopper.service.workflow.SimplifiedWorkflowServiceImpl.deleteExistingNamedEntitiesIfNecessary(SimplifiedWorkflowServiceImpl.java:893) at com.atlassian.greenhopper.service.workflow.SimplifiedWorkflowServiceImpl.createSimplifiedWorkflowForExistingProject(SimplifiedWorkflowServiceImpl.java:547) at com.atlassian.greenhopper.web.rapid.view.WorkflowResource$5.call(WorkflowResource.java:330) at com.atlassian.greenhopper.web.rapid.view.WorkflowResource$5.call(WorkflowResource.java:312) at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:42) at com.atlassian.greenhopper.web.AbstractResource.createResponse(AbstractResource.java:100) at com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:81) at com.atlassian.greenhopper.web.rapid.view.WorkflowResource.convertWorkflow(WorkflowResource.java:311) <+2> (DelegatingMethodAccessorImpl.java:43)
Workaround
There is no current tested workaround at this stage.
Attachments
Issue Links
- is caused by
-
JSWSERVER-12541 As an admin I want to be able to rename JIRA Agile Simplified workflow status names
- Gathering Interest
- mentioned in
-
Page Loading...