This seems like it could be mitigated with an integration that watches the issue tracker for updates and then commits those updates to a docs folder on the appropriate branch of the appropriate repo.
This would have saved quite a bit of headache at my last job actually.
Switching an existing project to a new VCS loses history or at minimum causes a new layer of "identifiers in the old system don't match the new one", no?
In general, I've found value in figuring out how to improve existing systems where feasible rather than trying to migrate to a new system, since the existing system probably has advantages the new one won't. At minimum, people are already familiar with the existing system.
Ah. I've spent a lot more time working on projects I inherited rather than ones where I made the initial technical decisions - if you're starting a new project, you should use the most capable tools available.
This would have saved quite a bit of headache at my last job actually.