Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,264
Community Members
 
Community Events
184
Community Groups

After programmatic move: How can I get Jira to find the issue by original issue key?

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

Hi @Rolf Dieter Zschau

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events