Hi @Eric Carlsgaard - Welcome to the Atlassian Community. You should be able to select the ellipsis on the top right corner of the ticket you are wanting to move. From there it should have a "Move" option. You can then select the project you are wanting to move the cloned ticket to.
If you don't have this option that means you don't have the "Move Issues" permission in that projects permission scheme. You will want to get yourself added to that permission. The move option should then be there after you are added.
Here is the Atlassian documentation on Moving Issues it also reminds that you should have create permissions in the target project as well.
Sorry @Eric Carlsgaard - My apologies I for some reason thought this was under JIRA Cloud. The Move option is under the More button on the JIRA issue view. If it doesn't appear there then that still means you don't have that permission, so you would still need to get that permission added for you. Here is the Atlassian Server documentation.
I had this requirement. I had multiple Epics, each with very similar tasks or stories ... varied very slightly (they were all migration initiatives). I found myself the quickest path to achieve what I wanted:
1. clone the story from Epic 1, create (or save): as mentioned above, you can choose clone from the list of items from the ellipses of the original story
2. Edit the cloned story or issue to taste.
3. move using .... move OR within the issue view, edit the Epic link by "clicking in" and then selecting from a list of Epics from the dropdown box.
4. you will find in your new Epic (Epic 2), the cloned issue associated with it.
Hope this helps :)
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events