XML exporting malfunction in Issues Navigator page

Jinrui Mai December 13, 2012

Enter Views > XML in Issues Navigator page ,there is a error showed like this:

An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getCustomFieldXML' in class com.atlassian.jira.issue.views.IssueXMLView threw exception java.lang.NoSuchMethodError: com.atlassian.jira.security.JiraAuthenticationContext.getUser()Lcom/opensymphony/user/User; at templates/plugins/issueviews/single-xml.vm[line 198, column 30] at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:351) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:262) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:342) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.directive.Foreach.performIteration(Foreach.java:393) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:316) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at

........

2 answers

1 accepted

0 votes
Answer accepted
Renjith Pillai
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 2, 2013

Is this really OnDemand hosted by Atlassian, it cannot be. This is an instance which is hosted by you.

This error is because of an outdated plugin which is still refering to "opensymphony.user"which is not available any more. Update all your plugins from UPM - https://confluence.atlassian.com/display/JIRA/Managing+JIRA's+Plugins.

Get rid of incompatible plugins and remove the custom fields coming from these incompatible plugins.

Jinrui Mai January 8, 2013

Yes,I found that may be relate to a custom plugin which developed by our company,I will try to fix it with re-compile the plugin jar in the new JIRA environment.

0 votes
JohnA
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.
December 16, 2012

Hi Jinrui,

I suspect the most likely cause of this issue is an incompatible plugin installed in your instance, so please ensure that all plugins are either upto date and compatible with your current version of JIRA, and if you cannot upgrade certain plugins then please disable them and reattempt the XML export again.

All the best,
John

Suggest an answer

Log in or Sign up to answer