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.
I suspect it's the renaming - you probably followed the info in http://confluence.atlassian.com/display/JIRA041/Advanced+JIRA+configuration+with+jira-application.properties# to do that.
The default is:
# The prefix added to the summary of cloned issues and the clone linktype name
jira.clone.prefix = CLONE -
jira.clone.linktype.name = 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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Meet @Dinesh Dhinakaran, @Vishnu Vasudeva, @Rajeev Verma, and Jamshid Nalakath: Our extraordinary AUG leaders from Bengaluru, India. These four work together to strengthen the bonds of their local co...
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!
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