The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue clone

Fredrik Ivansson Flinta
Contributor
April 21, 2021

Hi,

 

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

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Julie d'Antin [Elements]
Atlassian Partner
April 21, 2021

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!

DEPLOYMENT TYPE
SERVER
VERSION
8.5.3
TAGS
AUG Leaders

Atlassian Community Events