No, there is no "issue cloned" event. The internal systems don't really see a "clone", they see "new issue", even though all the data is scraped from an existing issue.
I suspect you need to trap a "create" event instead, then scan it to see where it was cloned from - you can look for the "clone" added to the summary, or the "was cloned from" link back to the original (although, it is possible to turn both of those off, and I'm stuck on how you'd detect a clone if that happens)
issuecreated doesnt seems to get triggered when a clone is created. so i couldnt really do anything there.
Also, In my case i disabled issue links "clone" and "was cloned from" so not sure how can i take it forward. Is there a way in which i can atleast disable cloning of issues?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
IssueCreated will definitely be fired... if it wasn't notifications wouldn't work for cloned issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah.. i was testing incorrectly earlier. IssueCreated is fired when a clone is created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.