Community
Q&A
Jira
Questions
JIRA 4.2 Cloned tickets are sending out notifications before saving

JIRA 4.2 Cloned tickets are sending out notifications before saving

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

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

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?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

A pop-up survey could appear while you're here --curious what it's for? Click here to learn more!

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

JIRA 4.2 Cloned tickets are sending out notifications before saving

2 answers

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events