Clone relationship is backwards

[Lauren Briskin]

Hi! When I clone subtasks, the resulting relationship seems reversed:

• Original (cloned) issue says "Cloned from"
• New issue says "Cloned to"

This results in things like this screenshot. An issue can't be cloned from two issues, so you can see it's backwards.

We're working through a punch list of field creation and configuration tasks, so there are dozens of these and it's really confusing to not be able to track correctly.

I see resolved tickets like https://jira.atlassian.com/browse/JRACLOUD-32042 from 10 years ago, but nothing more recent, which makes me think I'm doing something wrong?

Alternately, if this is a bug, is there a way to hide these issues so that the view is not cluttered with inaccurate and confusing information?

Thanks!

[Trudy Claspill · Accepted solution]

Hello @Lauren Briskin 

I suspect that somebody has change the Inward and Outward Descriptions associated with the Clones link type.

Below are the default descriptions for the Clones link type.

The value in the Inward Description will show in the issue you started the Clone operation from. The Outward Description will show in the issue created by the Clone operation.

In your system is "Cloned from" in the Inward Description, and "Cloned to" in the Outward Description?

Does this explanation align with what you are seeing?

[Lauren Briskin]

Thanks, that's very helpful!

I went to Issues > Settings > Issue features >> Issue linking >> Cloners (https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-linking/) and did see something that wasn't quite right. I've changed it to this, and I think it's better now:

Now I'll check if this triggered a reindexing. Thank you!