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

In the usual GUI, if an issue is moved between project, JIRA is capable of redirecting the user from the old URL to the new one with a HTTP code 302.

This feature would be extremely useful in the REST API as well if we're trying to get an issue using only the issue KEY (no search).

Use case:

• a user create an issue AAA-123
• Java app (API) using a search extract that issue to disk (or perform some work on the issue) and store the issue key (AAA-123) on disk.
• User move issue from project AAA to project BBB, resulting in BBB-234
• the REST API querying issue AAA-123 no longer find the issue (HTTP code 404 in REST)...

Expected result:

• the REST API allows the request to succeed, giving you BBB-234. The key field in the JSON will be BBB-234.
• the REST API should return a code 302 with the self URL of the moved issue to the new location. (JIRA will not 302 in this case)

BTW, I was hoping to workaround the problem with a JQL query like:

"issuekey" was "AAA-123"

but the "was" keyword doesn't seem to be present in JIRA 4.4.3.

That issue is also present in the SOAP API, although I'm sure fixing only REST would be sufficient as we're all moving that API anyway