It's basic, as Atlassian were given so many use cases, there's no way they could code for all of them.
You click "clone", and you get a new issue in the same project with all the same fields set the same as the original. As a new issue, the history and comments are removed, as they relate to the old one (Optionally, it prefixes the summary with "clone" and provides a link between the two)
There are a number of add-ons that do more - clone and move, and clone plus are the two I've used. You'd want to compare them for yourself (although I lean towards clone plus myself)
JIRA "Clone" feature will work for you if you just need a copy of a JIRA issue to/from a JIRA Project (NOTE: it has no dependencies or relationship at all, it's just a pure copy).
If you have to 2 separate JIRA instances, you can do a "Remote Copy" to your JIRA instance (This option will only appear if you have configured application links between your 2 JIRA instances).
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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