This would need to do something similar to what was asked earlier about detecting clones in a listener - https://community.atlassian.com/t5/Atlassian-Marketplace-questions/How-to-detect-via-script-listener-if-an-Issue-was-cloned/qaq-p/460724
Most of the answer is the same, except that you won't have an issue history to read, and will need to rely on the summary and/or link being set.
My problem is that i dont want to rely only on the summary, but the link collection of the cloned issue is empty during the create-postfunction (even when i move my custom script at the very end, ofcourse after "issue is created" step).
Collection<Issue> allIssueLinks = ComponentAccessor.getIssueLinkManager().getLinkCollection(issue, currentUser).getAllIssues()
=> allIssueLinks.size() is always 0. It works fine in other transitions but not during Create.
After cloning, i can see inside the issue history that first my script is performed and then the link is set afterwards ("user changed the Link to 'This issue clones ...").
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot