JIRA 4.2 Cloned tickets are sending out notifications before saving

Jeffrey Melies September 14, 2011

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?

2 answers

1 accepted

0 votes
Answer accepted
Jeffrey Melies October 30, 2012

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.

0 votes
Theodore Tzidamis
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 25, 2012

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?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events