It seems to work with Jira server 7.13.3.

When cloning issue, just make sure option "Clone sprint value" is disabled. I thought it was an option for story points, but it isn't.

Please reopen this issue. It is still a problem in Jira v7.13.5 server version.

Reopen issue and please fix this for the Jira server version.

Please reopen and then resolve this issue for the Cloud version of Jira.  Cloning an issue which was in a prior sprint still copies the sprint information. 

Unlike other agile work management tools, there is no way to select/ignore which fields are cloned and the defaults to not seem to make sense.

Thank you for your prompt and relevant action!

Clone Plus does support excluding fields with a customized clone action - see How to exclude fields from being copied to the clone.

My company is currently testing an upgrade to Jira Software 7.4.5 and the checkbox is available when Cloning an issue using the Jira clone option.  My company also use the Bob Swift Clone Plus plugin which enables the More options of Clone+ and Clone++.  This plugin does not support the ability for the user to choose whether or not to clone sprint values.  There are options with that plugin to choose whether to clone Watchers, Comments, and Sub-tasks.  I did find documentation for the Clone Plus plugin which documents the ability to not clone sprints by updating a property for the plugin: https://bobswift.atlassian.net/wiki/spaces/JCPP/pages/7012355/Clone+properties

This Issue is a big joke. It as more than 5 year now! mjopson, Could you please check a look at it ? Thanks!

Dear Atlassian,

can this issue be reopened please. It is NOT fixed. Sprints are still being copied while cloning issues, which is very annoying. 

This feature was not available in JIRA server 7.2.3 and is still not there in 7.3 and 7.4 ff.

As stated by Jeremy this feature is mentioned in the release notes 7.2. But the issue JSWSEVER-6541 is somehow NOT on the list of "Resolved issues 7.2".

Atlassian, can you please verify why this issue is marked as "Fixed" although it has not been rolled out yet.

Thank you!

Thank you for your attention to this problem!  Clone is a valuable feature that is currently worthless due to this problem.  We were forced to disable it in our organization to prevent the problems this creates with historical sprint data.

I completely agree with Jeremy, this issue is not solved. There is no configuration option (at least not for version 7.3.8) and the only work-around is the post-function fix that requires an expensive add-on to be installed.