JIRA 4.2 Cloned tickets are sending out notifications before saving

[Jeffrey Melies]

We are currently experiencing an issue where we Clone an existing ticket and notifications are being sent out before the ticket is being saved, thus appearing to be a duplicate issue, then the cloned ticket is modified and saved. Is there a way to stop the notifications from being sent out until after the cloned ticket is saved?

[Jeffrey Melies · Accepted solution]

Notifications were going out after clicking on "Clone", thus would include inaccurate information because the cloned ticket would be modified and then saved. This has been corrected after an upgrade.

[Theodore Tzidamis]

Hey Jeff,

I happened to bump into this old question. Is this still valid? If so, what do you mean "before the ticket is being saved?" Can you comment here with a simple scenario?