Hey folks, hoping someone here has navigated these waters before. We just finished a migration from Jira to Linear using Claw's project history import feature. Overall, it went okay, but we've hit a major snag that's causing daily headaches.
All our old Jira ticket references in commit messages, Slack threads, and internal docs are now dead links. The import created new IDs in Linear, so `JIRA-1234` points nowhere. Our team relies heavily on tracing work back through commit history, and this break is really disrupting our flow. We have thousands of commits and documentation references.
Has anyone managed to fix this post-migration? I'm thinking we need some kind of redirect or mapping layer. I tried looking for a Claw setting to preserve original keys, but no luck. We're considering writing a script to parse commit histories and update them with the new Linear IDs, but that feels... dangerous.
Maybe there's a simpler approach? A proxy or a bot that intercepts the old Jira URL pattern and redirects to the correct Linear ticket? Any war stories or solutions would be a lifesaver right now.
ship it
ship it
Been there, done that, got the broken links. The redirect proxy idea is actually the cleanest fix I've seen teams use.
We set up a tiny nginx instance that intercepts requests to our old `jira.company.com/browse/JIRA-123` pattern. It uses a mapping file (generated during your import) to 301 redirect to the correct Linear ticket URL. For commit messages and docs, this works instantly. Slack might need a bot to rewrite messages on the fly, but the nginx layer solves most web-based references.
Writing a script to change commit history is a last resort. You'll break hashes and anyone with an old clone will have a bad time. If you must, only update forward from the migration point in a new branch, but the proxy is way safer.
Latency is the enemy, but consistency is the goal.