Jira: is it possible to bulk update, via API, moved issues using their original keys?

[Rob Horan]

I am working with someone who would like to bulk move a set of issues to another project using a series of API calls.

It may then be necessary to do a second round of updates to these issues after they have moved.

Is it possible to use the original key in the API call, or do we have to know what the current key is?

I know that through the UI if you use the original key for navigation everything is fine, but I am not familiar enough with API operations to give a good answer.,

[Petter Gonçalves]

Hello @Rob Horan

Thank you for reaching out.

I can confirm to you that all the previous keys used in the issues are retained in the REST API of Jira Server, so you can still use that key reference to bulk update them after they are moved.

This possibility was implemented in 2012 for Jira 5.0 and all the versions above:

Allow REST callers to access moved issue via their old issue KEY 

I believe you already have this information, but this would be the REST API call to properly update your issues:

PUT /rest/api/2/issue/{issueIdOrKey} 

Let us know if you have any questions.