java.lang.IllegalArgumentException: Cannot find Screen with id '10322'.

Atlassian JIRA | Michael Ngangom [Atlassian] | 1 year ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    h3. Summary Not able to delete any screens because one of the screen has an invalid fieldscreen ID. Customer is modifying the field screen id of a screen in the exported workflow xml (the particular screen is used in a transition). The customer deleted the workflow in JIRA and imported the modified XML. All other screen which were deletable (and no changes were made to their fieldscreen.id) are now non-deletable. h3. Steps to Reproduce # Create 3 new screens (Screen A, Screen B, Screen C) # Create a new workflow that uses Screen C on a transition # Export the workflow to XML # Delete the workflow in Jira # Edit the XML and change the screen ID for Screen C to an invalid ID # Import the XML into Jira h3. Expected Results * Screen A and Screen B should be deletable. Any other screens which were deletable should have the 'delete' link and deletable. h3. Actual Results * Screen A and Screen B are non-deletable. The below exception is thrown in the atlassian-jira.log file: {code} 2015-10-09 10:35:48,135 http-nio-8070-exec-15 ERROR admin 635x309x1 b2jps5 0:0:0:0:0:0:0:1 /secure/admin/ViewFieldScreens.jspa [webwork.util.ValueStack] METHOD: "workflowTransitionViews", exception: java.lang.IllegalArgumentException: Cannot find Screen with id '10322'. at com.atlassian.jira.workflow.WorkflowActionsBean.getFieldScreenForView(WorkflowActionsBean.java:89) at com.atlassian.jira.workflow.AbstractJiraWorkflow.loadFieldScreenActions(AbstractJiraWorkflow.java:503) at com.atlassian.jira.workflow.AbstractJiraWorkflow.getActionsForScreen(AbstractJiraWorkflow.java:487) at com.atlassian.jira.web.action.admin.issuefields.screens.ViewFieldScreens.getWorkflowTransitionViews(ViewFieldScreens.java:164) {code} h3.Workaround The workaround mentioned in the Knowledge base article [Workflow error: Cannot find Screen with id 'xxxxx'|https://confluence.atlassian.com/pages/viewpage.action?pageId=295305313]. Below is the summary of the workaround: 1. Search for the workflow with that screen ID with the below SQL: {code}SELECT * FROM jiraworkflows WHERE DESCRIPTOR LIKE '%11100%';{code} 2. In the column DESCRIPTOR, there will be a line that used the screen ID from the error, for example: {code}<action id="791" name="Resolve Issue" view="fieldscreen"> <meta name="jira.description">1?????? ?? ???????.</meta> <meta name="jira.fieldscreen.id">11100</meta>{code} 3. Shutdown JIRA. 4. Update the database to change the screen ID, for example: {code}UPDATE jiraworkflows SET DESCRIPTOR = REPLACE (DESCRIPTOR, '<meta name="jira.fieldscreen.id">11100</meta>', '<meta name="jira.fieldscreen.id">3</meta>');{code} 5. Start JIRA.

    Atlassian JIRA | 1 year ago | Michael Ngangom [Atlassian]
    java.lang.IllegalArgumentException: Cannot find Screen with id '10322'.
  2. 0

    h3. Summary Not able to delete any screens because one of the screen has an invalid fieldscreen ID. Customer is modifying the field screen id of a screen in the exported workflow xml (the particular screen is used in a transition). The customer deleted the workflow in JIRA and imported the modified XML. All other screen which were deletable (and no changes were made to their fieldscreen.id) are now non-deletable. h3. Steps to Reproduce # Create 3 new screens (Screen A, Screen B, Screen C) # Create a new workflow that uses Screen C on a transition # Export the workflow to XML # Delete the workflow in Jira # Edit the XML and change the screen ID for Screen C to an invalid ID # Import the XML into Jira h3. Expected Results * Screen A and Screen B should be deletable. Any other screens which were deletable should have the 'delete' link and deletable. h3. Actual Results * Screen A and Screen B are non-deletable. The below exception is thrown in the atlassian-jira.log file: {code} 2015-10-09 10:35:48,135 http-nio-8070-exec-15 ERROR admin 635x309x1 b2jps5 0:0:0:0:0:0:0:1 /secure/admin/ViewFieldScreens.jspa [webwork.util.ValueStack] METHOD: "workflowTransitionViews", exception: java.lang.IllegalArgumentException: Cannot find Screen with id '10322'. at com.atlassian.jira.workflow.WorkflowActionsBean.getFieldScreenForView(WorkflowActionsBean.java:89) at com.atlassian.jira.workflow.AbstractJiraWorkflow.loadFieldScreenActions(AbstractJiraWorkflow.java:503) at com.atlassian.jira.workflow.AbstractJiraWorkflow.getActionsForScreen(AbstractJiraWorkflow.java:487) at com.atlassian.jira.web.action.admin.issuefields.screens.ViewFieldScreens.getWorkflowTransitionViews(ViewFieldScreens.java:164) {code} h3.Workaround The workaround mentioned in the Knowledge base article [Workflow error: Cannot find Screen with id 'xxxxx'|https://confluence.atlassian.com/pages/viewpage.action?pageId=295305313]. Below is the summary of the workaround: 1. Search for the workflow with that screen ID with the below SQL: {code}SELECT * FROM jiraworkflows WHERE DESCRIPTOR LIKE '%11100%';{code} 2. In the column DESCRIPTOR, there will be a line that used the screen ID from the error, for example: {code}<action id="791" name="Resolve Issue" view="fieldscreen"> <meta name="jira.description">1?????? ?? ???????.</meta> <meta name="jira.fieldscreen.id">11100</meta>{code} 3. Shutdown JIRA. 4. Update the database to change the screen ID, for example: {code}UPDATE jiraworkflows SET DESCRIPTOR = REPLACE (DESCRIPTOR, '<meta name="jira.fieldscreen.id">11100</meta>', '<meta name="jira.fieldscreen.id">3</meta>');{code} 5. Start JIRA.

    Atlassian JIRA | 1 year ago | Michael Ngangom [Atlassian]
    java.lang.IllegalArgumentException: Cannot find Screen with id '10322'.

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      Cannot find Screen with id '10322'.

      at com.atlassian.jira.workflow.WorkflowActionsBean.getFieldScreenForView()
    2. com.atlassian.jira
      ViewFieldScreens.getWorkflowTransitionViews
      1. com.atlassian.jira.workflow.WorkflowActionsBean.getFieldScreenForView(WorkflowActionsBean.java:89)
      2. com.atlassian.jira.workflow.AbstractJiraWorkflow.loadFieldScreenActions(AbstractJiraWorkflow.java:503)
      3. com.atlassian.jira.workflow.AbstractJiraWorkflow.getActionsForScreen(AbstractJiraWorkflow.java:487)
      4. com.atlassian.jira.web.action.admin.issuefields.screens.ViewFieldScreens.getWorkflowTransitionViews(ViewFieldScreens.java:164)
      4 frames