The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
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?
1 answer
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
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.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.