Just in case this is still relevant, I recently encountered the same requirement and found this helpful KB article:
Project and issue keys: Project keys are unique and can never be reused in Jira. If you migrate your issues to another project, they will get new keys and the new project must have a different key of its own. If you migrate your issues using the process above, Jira will automatically redirect any links to your old issue keys.
In our testing, when we moved a work item (issue) with a linked GitHub link, the Jira work item key was preserved. The work item remained accessible via direct link, global search, and JQL query using the original key. Furthermore, the GitHub links remained intact.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 21, 2024 edited
Hello, Good day. Gihub link are maintained using issue key. When you create a commit, push or merge request Jira issue key will be used to create the link on Jira issue. When you move issue between different project then this issue key changes causing the link to break.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.