IllegalArgumentException when searching for issues with specific statuses, or when loading the Workflows page in Jira server
Summary
- Searching for issues with specific status at Issue Navigator generates the below error.
- Trying to access Workflow menu at Administration >> Workflows >> Workflows generates the below error.
Environment
All versions of Jira Core 7.x and 8.x
Diagnosis
The following appears in the atlassian-jira.log:
2012-06-28 18:25:36,950 http-8080-3 ERROR [500ErrorPage.jsp] Exception caught in 500 page Cannot find Screen with id '11100'.
java.lang.IllegalArgumentException: Cannot find Screen with id '11100'.
at com.atlassian.jira.workflow.WorkflowActionsBean.getFieldScreenForView(WorkflowActionsBean.java:86)
at com.atlassian.jira.workflow.AbstractJiraWorkflow.reset(AbstractJiraWorkflow.java:432)
at com.atlassian.jira.workflow.AbstractJiraWorkflow.<init>(AbstractJiraWorkflow.java:48)
at com.atlassian.jira.workflow.ConfigurableJiraWorkflow.<init>(ConfigurableJiraWorkflow.java:26)
at com.atlassian.jira.workflow.OSWorkflowManager.getWorkflow(OSWorkflowManager.java:197)
at com.atlassian.jira.jql.context.StatusClauseContextFactory.checkWorkflow(StatusClauseContextFactory.java:179)2012-06-28 19:41:02,812 http-8080-3 ERROR admin 1181x361x1 us0a3v 127.0.0.1 /secure/admin/workflows/ViewWorkflowSteps.jspa [webwork] Error instantiating 'com.atlassian.jira.web.action.admin.workflow.ViewWorkflowSteps': com.atlassian.jira.web.action.admin.workflow.ViewWorkflowSteps doesn't have any satisfiable constructors. Unsatisfiable dependencies: [[interface com.atlassian.jira.workflow.JiraWorkflow, interface com.atlassian.jira.config.ConstantsManager, interface com.atlassian.jira.bc.workflow.WorkflowService, interface com.atlassian.jira.workflow.ProjectWorkflowSchemeHelper]]
org.picocontainer.defaults.UnsatisfiableDependenciesException: com.atlassian.jira.web.action.admin.workflow.ViewWorkflowSteps doesn't have any satisfiable constructors. Unsatisfiable dependencies: [[interface com.atlassian.jira.workflow.JiraWorkflow, interface com.atlassian.jira.config.ConstantsManager, interface com.atlassian.jira.bc.workflow.WorkflowService, interface com.atlassian.jira.workflow.ProjectWorkflowSchemeHelper]]
at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.getGreediestSatisifableConstructor(ConstructorInjectionComponentAdapter.java:138)
at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.instantiateComponent(ConstructorInjectionComponentAdapter.java:193)
at org.picocontainer.defaults.InstantiatingComponentAdapter.getComponentInstance(InstantiatingComponentAdapter.java:48)
at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42)
at org.picocontainer.defaults.SynchronizedComponentAdapter.getComponentInstance(SynchronizedComponentAdapter.java:35)
at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42)
at com.atlassian.jira.config.component.ProfilingComponentAdapter.getComponentInstance(ProfilingComponentAdapter.java:45)Cause
There is a workflow referring to a non-existent screen ID.
Resolution
If screen id is higher than 3
Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.
Search for the workflow with that screen ID with the below SQL:
SELECT * FROM jiraworkflows WHERE DESCRIPTOR LIKE '%11100%';
Remember to change the screen ID for the above SQL according to the error.In the column DESCRIPTOR, there will be a line that used the screen ID from the error, for example:
<action id="791" name="Resolve Issue" view="fieldscreen"> <meta name="jira.description">1?????? ?? ???????.</meta> <meta name="jira.fieldscreen.id">11100</meta> The Action ID '791' is using the screen ID '11100'.- Shutdown JIRA.
Update the database to change the screen ID, for example:
UPDATE jiraworkflows SET DESCRIPTOR = REPLACE (DESCRIPTOR, '<meta name="jira.fieldscreen.id">11100</meta>', '<meta name="jira.fieldscreen.id">3</meta>');The above SQL will change the screen for the transition to be 'Resolve Issue Screen'.- Start JIRA.
- Navigate to that Workflow and modify the screen, if required.
If after following the steps you continue to get the error when trying to edit the workflow, check if you don't have a Draft already created. If yes, then discard it and create a new one.
Please note the examples above are not to be taken exactly as they are displayed here since the IDs will most likely not be the same and may require a look into the fieldscreen DB table to choose the new ID for the specific transition.
If screen id is 1, 2 or 3
If the missing screen is such a low id, it's a Jira default screen that's used by some uneditable default workflows. The solution is to recreate the screen as advised in Screens are not showing Workflow Association and can not delete unused screens in Jira.
This is caused by a bug reported in JRASERVER-45713 - Getting issue details... STATUS