JMWE Create issue(s) post function

[Erik Berglund]

We are using the "Create issue(s) post" function on a transition in Jira Cloud to create multiple sub-tasks to users defined in a multi user picker field. 

Everything works fine, sub tasks are created, though it seems each sub task is created before Assigne field is changed to iterator {{it} causing the Create issue event to be fired and instead of {{it}} receiving emails abot the sub task,  the email is sent to the Projects Default Assignee

When we look at the sub task after created, the Assignee is correctly set but the History of the sub-task shows exactly the above process. ie

1) Create the sub-task

2) Change fields like for example Assignee

Is it possible to change this so that the sub-task is not created until all fields are set ?
Or is it something I can change on the post function to get the create issue notification correct?

Any help would be greatly appreciated. 

[David Fischer · Accepted solution]

My guess is that the Assignee field is not on the Create screen, forcing JMWE to first create the issue without the Assignee and then setting the Assignee field. Can you check that?

[Erik Berglund]

That was it! We had a simple workflow and screen associated with this custom sub-task type. Did not know that the altered fields actually had to be on the Create screen. But now I know :-)

Thanks !

[David Fischer]

Well, that’s the point: they don’t have to, but if they aren’t, they will be set after the issue creation.