This has shipped earlier in the year as part of 3.1 for Server. See the release notes for a description and the link to documentation.

Service Desk 3.1.0 has the new link in it (aka core 7.1 and higher).

I have the same as William. No "Create linked issue" on my on-premise installation, v7.0.10

When I go to an issue and click the "More" button I do not see the "Create Linked Issue" option. Only "Link" option. I'm on standalone version 7.0.5 build 70114.

I am not seeing the option either. Please explain how this works. Thanks!

@Andy Fleming: Where is this feature, since I have ServiceDesk on-premise, newest version, and not sure how to find "Create Linked Issue" as button, link, menu options, mind-reading module, etc?

There's now a Create linked issue option for JSD issues which effectively provides this functionality.

Does pretty much what we originally asked for...

Would love to know how Atlassian handles this? How do you triage support cases from the Support Desk to your dev project(s)? I was just about ready to leap full into adopting Service Desk as I got tired of waiting for Help Scout to do a JIRA integration, and hit this wall. We'd be in the same boat - having to manually create issues in our dev projects for dealing with customer support incidents.

We too move tickets to internal projects via clone then move. This has always been awkward but is way worse now that there is an auto-responder every time you create a ticket. Cloning is seen as a create in SD, so it fires all automation rules AND sends the customer the 'we received your ticket' email for a second time. Which, c'mon guys... Can't turn notification off, can't treat clones differently (all are new), and can't hack your way around it in cloud. Killin me smalls!
@Bob Cloud compatibility would be the best Christmas present ever!!!!

@Bob - THAT is exactly what we need in our Cloud instance!! I so hope you get Cloud support working before the end of the year. Thanks! +1 Bob Swift & Clone Plus for JIRA!!!

This requirement is solved by the customization support provided by Clone Plus for JIRA. You can define a customized "clone" action named whatever you like (example: Create a developer ticket). This can be tailored to cover most use case. We have put together a how to - How to Clone issues from Service Desk To Development. This is available for server with Cloud support planned in the coming months.

@Brian - agreed. Frankly it's not much of a product without this MVP feature.

Ugh! How can this STILL not be a feature when it would save SO much work for support and team leads??

PLEASE add this in!!! ... I was sure this was going to be a no-brainer reason to switch from two different non-JIRA ticketing systems to JIRA to make it so easy to flow issues from our Customer Support department to Development. It is a much harder sell to my CEO and other stakeholders when there is so much manual re-typing and potential for mistakes if you get interrupted and don't link back to the original ticket.

I'd like to add (for the benefit of the afflicted ) that the ClonePlus plugin from Bob Swift seems to a) give one the ability to clone+move in one step without a temporary cloned ticket in the source desk project, b) without emailing the user of said temp ticket, which was said to be confusing to some, and c) where you can set/change destination fields in one step. Also looked at the "Create On Transition" plugin for making this automated, but I don't think it allows as much control as we need on cloning to the right project.

This is precisely the functionality I am evaluating SD with JIRA for.
Atlassian: How do you manage this workflow within your operations? Or are you not using SD for customer issue intake?

What I was looking for and expecting Service Desk would handle in first place.. but bummer.. vote up for this.. This is much needed for Development and Service desk shop like ours.

+1 We could also make use of this feature. Use case is similar to the one described by the reporter

This is an ongoing issue for us. We have 3 helpdesk agents that field issues, only some of which turn into tickets for a separate team of four developers to work on in various (non-SD) JIRA projects. Right now, the only option is to clone-then-move. Somewhat inconvenient, and it generates emails on that temporary SD ticket that is confusing to user. We need a "Copy To" that combines clone + move into a one-page operation, with a separate notification type that can be managed in the notification schema.

PS: We also use a separate plugin to merge some data from the copied ticket back into the helpdesk ticket, although a better solution would be for a ticket to co-exist in two projects like I requested in JSD-2112.

PPS: Why does it have to be four roundtrip steps to move? I understand that some subsequent choices are based on previous values, but that can be done all on one page with appropriate server calls and JavaScript.)

it would be great if we have this option in Jira SD

I second this request.

It would be awesome if Service Desk Agent can copy and link issue to the development project with one button. If developer finishes the linked issue, Service Desk Agent gets notified and can continue on resolving customer's case.

This function is exactly what I was looking for, and a big part of why we have been considering Jira Service Desk. We are a software development shop, and would like our client service team to manage client inquiries, reports, and bug reports via Service Desk. Once they have planned out the scope of a client deliverable, they would push the information over to development. Ideally, the Service Desk tickets would then be updated that they were in development, which would certainly aid our Project Managers in their status meetings with clients.

This would be great. A way to have a ticket cloned into another project, and also the ability to map workflow steps from that new ticket into the desk ticket. That way, as it goes into statuses for feedback or resolution, that gets reflected back into the desk ticket. Look at FreshService integration with JIRA for an example.