Hello everyone,
we've got two jira instances synching issues from instance A to instance B by exalate.
In the creation phase, exalate fills our customfields and immediately afterwards (still creation phase) antother postfunction (provided by our jira plugin) reads that customfield and edits it. But somehow it isn't possible to set the new value, because jira seems to reject it during the whole creation phase.
Do we have any possibility forcing jira to free that customfield to be able to set it?
Thanks for your help!
