JIRA NullPointerException when switching Workflow scheme

Hi all,

I have a problem since I imported a workflow as xml and assigned it to a production project. The workflow itself worked fine on my test system and also looked fine as a diagramm in production.

I noticed in production that in the Workflow Text-Modus 3 Step-Names are not linked with the proper Status and 2 don't have any:

Now, although I changed this missfits, I can't assign the new Workflow (Workflow-Scheme) or the old one to the Project, since I keep getting the same java.lang.NullPointerException:


Stack Trace: [hide]

	at com.atlassian.jira.web.action.admin.workflow.scheme.SelectProjectWorkflowSchemeStep2.getSelectListName(SelectProjectWorkflowSchemeStep2.java:255)
	at com.atlassian.jira.web.action.admin.workflow.scheme.SelectProjectWorkflowSchemeStep2.addMigrationMappings(SelectProjectWorkflowSchemeStep2.java:181)
	at com.atlassian.jira.web.action.admin.workflow.scheme.SelectProjectWorkflowSchemeStep2.doExecute(SelectProjectWorkflowSchemeStep2.java:120)
	at webwork.action.ActionSupport.execute(ActionSupport.java:165)
	at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:82)
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39)
	at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31)
	at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16)
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35)
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:221)
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:150)
	at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:153)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)

Can anyone help please?
Many thanks!

4 answers

1 accepted

Problem solved:


Two steps had no linked statuses, therefore the nullpointer exception.

I created two temporary statuses (Administration >> Issue Settings >> Statuses > Add New Status). These new statuses automatically got the id's that were missing, and that the pointer was pointing to. After that the exception was gone and I could replace the scheme.

try with the jelly script

<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.enterprise.JiraTagLib" xmlns:core="jelly:core" xmlns:log="jelly:log">
  <!-- Grab managers. Do it using ComponentAccessor now which gives better compatibility in Jira 5! r -->
  <core:invokeStatic className="com.atlassian.jira.component.ComponentAccessor" method="getWorkflowSchemeManager" var="workflowSchemeManager"/>
  <core:invokeStatic className="com.atlassian.jira.component.ComponentAccessor" method="getProjectManager" var="projectManager"/>
  <!-- Get the project with key "MYPROJECT" using ProjectManager -->
  <core:invoke on="${projectManager}" method="getProjectObjByKey" var="project">
    <core:arg type="java.lang.String" value="MYPROJECT"/>
<log:warn>Project ${project} found</log:warn>
  <!-- Get the workflow scheme "myScheme" -->
  <core:invoke on="${workflowSchemeManager}" method="getSchemeObject" var="scheme">
    <core:arg type="java.lang.String" value="myScheme"/>
<log:warn>Scheme ${scheme} found</log:warn>
  <!-- Assign scheme to project -->
  <core:invoke on="${workflowSchemeManager}" method="addSchemeToProject" >
    <core:arg  value="${project}"/>
    <core:arg  value="${scheme}" />

check this


The Jelly Script didn't work:

Could not run script.
Extra Information: [hide]

Error: <JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.enterprise.JiraTagLib" xmlns:core="jelly:core" xmlns:log="jelly:log">
Exception: org.apache.commons.jelly.JellyTagException: null:21:0: No such accessible method: addSchemeToProject() on object: com.atlassian.jira.workflow.DefaultWorkflowSchemeManager

on which version of jira you tried?

i tried the same jelly script and get the same error (jira 5.1.8). do you have any information, how i can assign a scheme with jellyscript in my jira version?


Sorry, we have v5.2.6

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,063 views 13 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot