Epic link is lost when moving issues between projects
Keep stories attached to their epic across a project move.
Reorganising projects shouldn’t orphan your stories. Here is how to keep the epic link intact across a move.
The symptom
You move a story to another project and its epic link silently disappears. The issue lands orphaned and the epic now rolls up the wrong scope.
Why Jira behaves this way
During a move Jira remaps project-scoped fields, and the epic association is dropped rather than re-linked when a matching epic exists in the destination.
The manual workaround — and why it falls short
Teams note each story’s epic before the move and re-link them one by one afterwards, which is slow and easy to get wrong across a large move.
How Patcher fixes it
Patcher preserves the epic link across project moves where a matching epic exists and flags the ones that need attention, so your hierarchy survives the move.
Turn it on
- Install Patcher for Jira from the Atlassian Marketplace.
- Open Patcher › Patches from your Jira admin.
- Find Preserve epic link on move in the list and switch it on.
- Scope it to the projects you choose, then save — the fix is live immediately.