Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,555,446
Community Members
 
Community Events
184
Community Groups

Check if Issue is a clone during create postfunction (customscript)

Hi,

can I check within a custom script postfunction (directly after create) if an issue is a clone or not? 

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 10, 2017

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 ...").

Hello Dennis,

 

Did you find any workaround for this?

 

Regards,

Moiz

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events