Unfortunately the field values are not the same so I can't use mapping to map the values between the new/original issue. To potentially add to the level of difficulty, the post transition is a quick transition triggered as an action from another regular transition and so is the submit transition into the new project - so at the moment there is no user involvement at all when the new issue is posted - and the users want to leave it that way.
Any thoughts on how best to achieve this.
Accepted AnswerFranz AndelOffline0Just an untested (in the post transition context) thought :
you could add an orchestration workflow to your post transition that uses
-GetItem (sbmappservices72) to read the field(s) from your "old" application
-some calculate steps to manipulate/transform your data
-TransitionItem (sbmappservices72) to write the field(s) to your "new" application
The complexity of the orchestration depends on the type of fields that you want to "copy"/create.
Accepted AnswerEmployeeLynn MattieOffline0Or you can run an AppScript on the post-transition of the submit transition and that can read the original item and then set values in the new item. In order to make the read of the original item easier, make sure you have a field in the new item that points to the original item that is set by the Post transition that created the new item.
Accepted AnswerDavid SheaffeOffline