You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I managed to move an issue programmatically (groovy script using Script Runner, running as escalation service) from one project to another, migrating the workflow using migrateIssueToWorkflow of WorkflowManager. So I used a code similar to https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-move-an-issue-programatically-to-a-different-project/qaq-p/515955. My special configuration allows for a specialized case, so that this is working. I also managed to enter change history entries that look similar to entries of a manual move using UI.
So far so good.
But compared to the manual move using UI I'm still missing, that the issue is found by searching for original issue key. What entry do I have to make / what methods of what objects to use, so I get that working?
Were you been able to solve this problem? I have the same question. I can't get the issue by its original issue key and all the references in comments, links...has been lost.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.