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:

Cause:
java.lang.NullPointerException

Stack Trace: [hide]

java.lang.NullPointerException
	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

Accepted Answer
1 vote

Problem solved:

https://confluence.atlassian.com/display/JIRAKB/%27NullPointerException+in+SelectProjectWorkflowSchemeStep2.getNumAffectedIssues%27+Due+to+Workflow+Step+that+Doesn%27t+Have+a+Linked+Status?src=search

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"/>
  </core:invoke>
<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"/>
  </core:invoke>
<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}" />
  </core:invoke>
 
 
</JiraJelly>

check this

https://answers.atlassian.com/questions/47591/associate-workflow-schema-to-project-using-jelly-script

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
java.io.PrintWriter@1f5e5a8e

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?

regards

Sorry, we have v5.2.6

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

41 views 0 2
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