Moved Issues no longer redirect from previous Issue key or URL in Jira
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When an Issue is moved from one Project to another in Jira, accesses to the previous Issue key or URL are automatically redirected to the current key or URL.
If an Issue is moved several times to different Projects, or even back to a previous Project, all the keys and URLs the Issue once had are stacked up and redirected to the current Issue key and URL.
Environment
Any Jira Software or Service Management with installed Apps (plugins) that provide scripting functionality or functions that allow moving an Issue.
Diagnosis
1) Moving Issues through Jira's native feature works
Moving an Issue through Jira's native feature available on the More > Move menu works as expected. All Issues past keys and URLs redirect to the current key and URL.
2) Moving Issues through 3rd party apps features doesn't work
Several 3rd party apps provide features that allow moving Issues to other Projects through other means than the UI menu. They include:
Workflow post-functions (ie. the Issue's moved through a workflow transition)
Automations
Scheduled routines
If moving an issue through these means doesn't (consistently) preserve the old key or URL but the native feature (item 1) does, this resolution suggested below should apply.
3) DB table missing data (optional)
A further confirmation can be done by querying the database for the new issue key. Replace 'NEW' and 12345 below for the respective current Issue's key (NEW-12345):
1
2
3
4
5
select m.*
from jiraissue i
join project p on p.id = i.project
left join moved_issue_key m on m.issue_id = i.id
where p.pkey = 'NEW' and i.issuenum = 12345;All past Issue keys should be present in the output, even if back-and-forth on the same Project. Missing records are the reason why the automatic redirects aren't working.
Cause
When an Issue is moved in Jira the table moved_issue_key is updated with the now-previous Issue key.
3rd party apps may use Jira's Java API directly and may contain bugs that result in the moved_issues_key not being properly updated — or may have another function/method/routine that works instead.
Solution
You should contact the third-party app vendor for support on this. They may offer a workaround or investigate whether it's indeed a bug in their app and which version it's been fixed in.
Alternatively, you may use another third-party app that provides a similar "move Issue" feature if you have them installed.
And last, resorting to Jira's native More > Move feature in the meantime.
Was this helpful?