Issue 168 in jira-suite-utilities: Could not load FunctionProvider class error after Jira 4.0 to 4.2.2 upgrade

210 views
Skip to first unread message

jira-suite...@googlecode.com

unread,
Mar 2, 2011, 6:04:56 PM3/2/11
to jira-suite-utili...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 168 by brandon....@gmail.com: Could not load FunctionProvider
class error after Jira 4.0 to 4.2.2 upgrade
http://code.google.com/p/jira-suite-utilities/issues/detail?id=168

What steps will reproduce the problem?

1. Configure JIRA 4.0 instance running Jira Suite Utilities 0.7.0 with
workflow transitions that include the following pre-function:

<pre-functions>
<function type="class">
<arg
name="class.name">com.opensymphony.workflow.util.Caller</arg>
</function>
<function type="class">
<arg name="field.value">${caller}</arg>
<arg
name="class.name">com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction</arg>
<arg name="field.name">assignee</arg>
</function>
</pre-functions>


2. Upgrade to JIRA 4.2.2 and Jira Suite Utilities version 0.7.16.
3. Run a transition that calls the pre-function above and you will receive
a "Could not load FunctionProvider class".

What is the expected output? What do you see instead?

Should not receive an error and the transition should succeed as it did
with Jira 4.0 / Jira Suite Utilities 0.7.0.

What version of the product are you using? On what operating system?

Working: Jira 4.0 / Slackware / Jira Suite Utilities 0.7.0
Broken: Jira 4.2.2, 4.2.3, 4.2.4 / Slackware / Jira Suite Utilities 0.7.16

jira-suite...@googlecode.com

unread,
Mar 3, 2011, 3:23:51 AM3/3/11
to jira-suite-utili...@googlegroups.com
Updates:
Status: Invalid

Comment #1 on issue 168 by abas...@gmail.com: Could not load

FunctionProvider class error after Jira 4.0 to 4.2.2 upgrade
http://code.google.com/p/jira-suite-utilities/issues/detail?id=168

I'm sorry but I don't know how to correctly configure Jira workflows with
XML. Please use web interface for that stuff. Also placeholder for current
user always was %%CURRENT_USER%%

Reply all
Reply to author
Forward
0 new messages