Unable to move issues with attachments

[heineja]

When users attempt to move issues that have attachments on them, they get a null pointer exception. For example, a user is moving issue ABC-191 to XYZ. I can see that the 4 attachments on ABC-191 have moved to the XYZ/XYZ-480 directory. But for some reason, jira is still looking for the attachments in the original directory - ABC/ABC-191. So it seems to move the attachment, then look for them in the old directory, then throw a null pointer exception.

One thing to note, our default attachment path is a symbolic link.

2013-01-29 09:29:06,024 http-bio-8080-exec-41 WARN

/secure/CommentAssignIssue.jspa jira.plugins.webhooks.WebHookRegistrationManager Failed to publish web-hooks for event com.atlassian.jira.event.issue.IssueEvent

java.lang.NullPointerException: null value

at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:204)

at com.google.common.collect.ImmutableMap.entryOf(ImmutableMap.java:139)

at com.google.common.collect.ImmutableMap$Builder.put(ImmutableMap.java:178)

at com.atlassian.jira.plugins.webhooks.mapper.EventTypeInfoDecorator.toMap(EventTypeInfoDecorator.java:28)

[heineja · Accepted solution]

issue was that project ABC has a custom field set that project XYZ does not have set. in this case, the issue cannot be moved from ABC to XYZ unless the custom field is removed from ABC or added to XYZ.

[C_ Faysal]

i bet the symbolic link causes this....

how was is created?

[heineja]

created on the linux side with ln -s. is there another option? is it possible to change the default attachment path?