Cloned issues are not being linked to original

Hi, after our import into JIRA Studio from our local JIRA server, cloned issues are no longer being linked to the original. I believe we renamed the Link Type for this in our local server and perhaps this change didn't persist when we migrated to JIRA Studio.

It's not urgent but it was definitely a nice to have as we sometimes need to clone/move issues into a different project and having it automatically add the link was helpful.

1 answer

1 accepted

Accepted Answer
1 vote

I suspect it's the renaming - you probably followed the info in to do that.

The default is:

# The prefix added to the summary of cloned issues and the clone linktype name

jira.clone.prefix = CLONE - = Cloners

So I'd suggest (temporarily) creating or renaming a link type as "Cloners" and see if that does the linking correctly. If it does, then that's the problem, and you can either go back to using "Cloners" or contact OnDemand support to see if they can change it to match your link name.

Thanks Nic. That looks to have been the case. An OnDemand support engineer corrected the problem for me.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 10 hours ago in Jira Ops

Jira Ops Early Access Program Update #2: Let’s talk severity levels

Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...

21 views 0 0
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you