Workflow exception - could not load FunctionProvider class

Ashley Kim January 16, 2017

While importing data in JIRA, I got the following error message. 

JIRA server - version 6.4 

Is it because there are missing add-ons? 

Any idea?

 

============================================================================

ERROR 01:42:41,570 Unable to create issue with key 'OL-9'.

com.atlassian.jira.external.ExternalException: Unable to create issue: OL-68
at com.atlassian.jira.external.ExternalUtils.createIssue(ExternalUtils.java:246)
at com.atlassian.jira.imports.project.DefaultProjectImportPersister.createIssue(DefaultProjectImportPersister.java:147)
at com.atlassian.jira.imports.project.handler.IssuePersisterHandler$1.run(IssuePersisterHandler.java:78)
at com.atlassian.jira.util.concurrent.BoundedExecutor$1.run(BoundedExecutor.java:58)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.atlassian.jira.exception.CreateException: com.atlassian.jira.workflow.WorkflowException: Could not load FunctionProvider class
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:671)
at com.atlassian.jira.external.ExternalUtils.createIssue(ExternalUtils.java:235)
... 6 more
Caused by: com.atlassian.jira.workflow.WorkflowException: Could not load FunctionProvider class
at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:916)
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:658)
... 7 more
Caused by: com.opensymphony.workflow.WorkflowException: Could not load FunctionProvider class
at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:1046)
at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1446)
at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:615)
at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:886)
... 8 more

3 answers

0 votes
Ashley Kim January 18, 2017

Thank you, all! 

I found a missing add-on while going through postfunction of workflow transitions! 

I could finally import the project !

 

Asha Ganesh November 2, 2018

hi ,Can u please mention how u found the add-on 

or kindly suggest the addon

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 2, 2018

They went over the post-functions in the workflow, which will usually tell you which (missing) class is being called.  Most add-ons give their classes distinct names which can tell you, or at least allow a web search for the name of the add-on

Like Asha Ganesh likes this
0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 16, 2017

Also, if you read further down the log, you *might* find a "caused by" entry with the class of the missing add-on named.

0 votes
Vasiliy Zverev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 16, 2017

It seems that it really caused by some add-on. Could you provide list of postfunction on create transition?

Suggest an answer

Log in or Sign up to answer