For several reasons I had to migrate main Jira project, let's say 'CENTRALPRJCT' from 'Jira A' to another Jira Server 'Jira B' (both on-prem) - worked ok.
On 'Jira A' the migrated project is untouched, up to now (but for obvious reasons it is read-only). Now several other projects on 'Jira A' are still linking (local issue links) to meanwhile orphaned 'CENTRALPRJCT' on 'Jira A'.
(?) Question: Is there any, programatically way, to "convert" all local issue links in several hundred projects on 'Jira A' to the same named project - meanwhile on 'Jira B'??
As this only affects the one moved project all other issue links must remain untouched.
Any hint or advise is appreciated.
BTW: I was able to fix the "Jira B"-side using: https://developer.atlassian.com/server/jira/platform/using-fields-in-remote-issue-links/
(!) Using this I was not able to create a reciprocal link though - and that's why I am asking here now on to if there is a chance to get the remaining projects on 'Jira A'-side fixed as well...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events