Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage



When using Issue clone why does the Clone gets issue link: "clones (outward)" ad the parent gets: "is cloned by (Inward)?


Shouldn't it be the otherway around? "Parent: clones (outward)" and the "Clone: is cloned by (Inward)? 



1 answer

1 accepted

Hi, I think it helps to think of it as the clone doing the acting, whereas the original issue (parent issue) is the passive one.

If you create a sub-task for a task and set a blocking link, generally it will be in the same way. For example the sub-task (which you create after the original parent task) blocks the parent task, and the parent task is blocked by the sub-task. As long as you don't finish the sub-task you can't finish the parent task. And again it's the second issue created that is the active one, and the parent issue remains passive.

Hope that helps!

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you