#635 JDODetachedFieldAccessException when changing Issue status

[jfirechief]

DO NOT EDIT OR ANSWER THIS ISSUE. SEE THE ORIGINAL ISSUE INSTEAD:
https://www.jfire.org/modules/bugs/view.php?id=671
ORIGINAL REPORTER: alex

javax.jdo.JDODetachedFieldAccessException: You have just attempted to access field "issueLocal" yet this field was not detached when you detached the object. Either dont access this field, or detach it when detaching the object.
at org.nightlabs.jfire.issue.Issue.jdoGetissueLocal(Issue.java)
at org.nightlabs.jfire.issue.Issue.getStatableLocal(Issue.java:599)
at org.nightlabs.jfire.jbpm.ui.state.CurrentStateComposite.setStatable(CurrentStateComposite.java:110)
at org.nightlabs.jfire.jbpm.ui.state.CurrentStateComposite$2.run(CurrentStateComposite.java:93)
at org.nightlabs.base.ui.job.Job.run(Job.java:53)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Happens when changing the status of an issue.

[jfirechief]

Logged In: YES
user_id=1828570
Originator: YES

ORIGINAL COMMENT BY alex, VIEW IT HERE:
https://www.jfire.org/modules/bugs/view.php?id=671

The same seems to happen when assigning a user to the issue.
It somehow changes the status as well.

This feature (status-assignment-coupling) does not work reliably. I will create a new issue for that (->0.9.6). An we should disable this functionality for the 0.9.4 release.

However, changing status and assignment should work indenpendently in 0.9.4.