Usually when I clone tickets the original ticket is linked to the new cloned ticket but now it does not happen. Is there a new setting I need to enable for this?
Solution:
The Issue Linking name has been renamed at some point in the past for Clones in the issue linking configuration. It needs to be named Cloners.
Hello @emmy
How are you cloning the issue?
Are you using the Clone option from the Actions menu of an individual issue? Do you see more than one Clone option there?
What type of issue are you cloning; an Epic, a "standard" issue, or a "subtask" issue?
Are you cloning issues in a Company Managed project or in a Team Managed project?
If you look at manually linking an issue do you still see options for clones/is cloned by?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'll be on a ticket (task, story) then click the three dots at the top right of the ticket > select "Clone" > automatically clones the ticket
The new cloned ticket does not have the original ticket linked, it used to do that automatically or atleast ask to link the ticket by checking a box before cloning.
Projects are all company-managed.
I still see the options clones/is cloned by.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you able to manually create a link between the new issue and the source issue in this project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you look at the History of the issues, do you see that the link was initially created and then removed?
In my Jira Cloud system the issues are linked automatically. In Jira Server/DC this could be configured so that the link would not happen, but that option is not available in Jira Cloud, so the link should be getting created.
The two thoughts I've had is that perhaps you don't have the Link permission in the project, or an Automation Rule is removing the link after it is created.
If neither of those applies, then I recommend that you open a support case directly with Atlassian for additional help. And it would be great if you can report back here what you learn.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@emmy Did you get a solution to this issue? I'm seeing the same in our Jira Cloud system.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.