This seems like a "Clone" where fields are pre-populated but not all fields are editable (like the Sprint field). We should have the ability to update each field that is pre-populated.

Please don't flame me for this comment - I know the ticket itself was to add the capability natively into Jira SW server, and indeed that is why I started watching this ticket years ago.  But after seeing the comments go back and forth about differing thoughts on what really should (imo) be configurable, I wanted to throw out there that after getting frustrated about the missing 'core' feature, we bought the app STAGIL Issue Templates and really could not be happier.  it is a little complicated now (it has gotten more so over the past couple years as they merged 'templates' into it) but it allows you to configure exactly which fields you want to copy, offer to change, etc based on issue type, project, etc.  and you can have more than one option on the menu, which creates different-setup links as needed.  I am in no way affiliated with the vendor, just a happy customer.  hope it helps.

William: "Need option to turn off "Create Linked Issue" duplication of Summary and Description."

I think we use different ways "Create linked issue" function. In our Jira, "Clone" function is disabled because it is allows users to skip statuses and COPY workflow like values (like resolution). "Create linked issue" is a way to replace "Clone" function. So the main benefit is that they can COPY Summary and Description and basic values to the new issue (which is a basic needs). So turn off this feature makes this function useless to us.

In other hand: If "Clone" function could be more regulated (administrators could set rules who and what can Clone), that would be an alternative solution for my problem.

Kindly disagree with William: Clone function ALLOW users to copy almost ALL details of original issue (for example status, resolution, date-time values, etc.). "Create linked issue" is like an advanced Create function where you can COPY Summary and Descriptions and Links and Attachements and Required fields (so you can CLONE them), but the new issue will start at the first status (Open) and do not inherit workflow like values (as resolution).

Other option: IssueType field should be EMPTY to WARN users they HAVE TO choose the correct IssueType.

In general, there is the first IssueType or the last used IssueType what "Create linked issue" function offers. This is root cause of many mistakes.

Disagree with "Create linked issue" that would be nice if it is offer original issuetype. That what Clones are for. The new for Planning to flowdown their Features/higher to many teams and their Epics/Stories is a great need for a larger company. That need is being killed by copying all an issues info to a Team-level issue - unless there is an option to not auto-populate the fields. This is becoming a good idea gone bad.  

One more thing: If you use "Create linked issue" that would be nice if it is offer original issuetype as default on create view. Lot's of user just create the issue as COPY, but than realize it has got a different issuetype. That could be an option to choose different issuetype (not by default).

Need option to turn off "Create Linked Issue" duplication of Summary and Description. We like the "Create Linked Issue" but users want to turn off the auto-population of Summary and Description text. Their summary and description is different from that of the Epic and the duplication causes is confusion. I'm sure it is nice feature for some, but we want the option to turn off the duplication. I not seen any options to do this in the documentation, blogs or Jira Admin.

10/19/23 It seems even worse now (9.10) - to the point that users no longer want to use it. It used to auto-populate only a few fields, but now it is many. That mean users have to delete the content in many fields in order to avoid wrong information in their issue. Examples: wrong Sprint, wrong Label, wrong relationship, wrong custom fields, ... Please have a way to turn of the automated population. This isn't used to clone, it is used to create many child issue for an issue (e.g., for an Epic). Duplicating the fields is usually not help and just adds work and errors.  

David Yu: can you expand on what the link code does? I presume that this is the call to create a new issue but how does it work? Are the parameters from the original issue held in "$H"? 

#set($H = '#')$H

I ask because I'm trying to work out how to disable "Create Linked Issue" for specific projects.

OK. I understand that this is problematic because of Sprints. But Clone function is more problematic. Please make it possible to use this function in Software project type as well.