Associating Workflow For 'Error rendering WebPanel (workflows/workflows.vm)' Error

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

When the error "Error rendering WebPanel (workflows/workflows.vm)" is thrown it is a product of this KB:Exception When Viewing 'Workflow Schemes' Via Project Administration. In JIRA 5.x, the Project Workflow page is not editable, hence you cannot associate a new workflow into the project.

(Auto-migrated image: description temporarily unavailable)
1 Error rendering WebPanel (workflows/workflows.vm): org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.jira.web.component.IssueConstantWebComponent threw exception java.lang.NullPointerException at workflows/workflows.vm[line 136, column 65]

Diagnosis

User will not be able to change the workflow association due to the error. This only happens in JIRA 5.x.

Resolution

Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.

  1. Perform the workaround that was given in this KB first: Exception When Viewing 'Workflow Schemes' Via Project Administration

  2. Copy the broken workflow and associate them with the correct status

  3. Create a new Workflow Scheme and associate that scheme with the workflow created from step number 2

  4. Stop JIRA

  5. Run the following query in your database, and record the ID retrieved:

    1 SELECT * FROM workflowscheme WHERE name LIKE '%workflowname%';

    ℹ️ Replace workflowname with the workflow you created on step number 3

  6. Run the following query to check what is the workflow scheme associated with the project

    1 SELECT * FROM nodeassociation WHERE source_node_id = (SELECT id FROM project WHERE pkey LIKE '%TEST%');

    ℹ️ Replace TEST with the project key of the affected project

  7. After confirming, update the workflow association with the workflow scheme ID obtained from step number 5

    1 UPDATE nodeassociation SET sink_node_id = 10000 WHERE sink_node_entity LIKE '%WorkflowScheme' AND source_node_id = (SELECT id FROM project WHERE pkey LIKE '%TEST%');

    ℹ️ Replace the sink_node_id with the id obtained from the result of step number 6, and pkey of the project that is affected

  8. Restart JIRA

  9. Run Integrity Checker Tool, to confirm if there is any inconsistencies

  10. Navigate to the Project Workflows page to check whether you could change the workflow association now

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.