You cannot transfer a Google Doc comment thread to a Jira ticket without manually copying it

Your team discusses a feature in a Google Doc. There are 15 comment threads with decisions, edge cases, and open questions. Now you need to create a Jira ticket to actually build it. You must manually read each comment thread, summarize the decisions, copy relevant quotes, and paste them into Jira. Links back to specific comment threads in Google Docs break when the doc is restructured. So what? The context that matters most — why decisions were made, what alternatives were rejected, what edge cases were identified — is permanently trapped in Google Docs comments and never makes it to the ticket. The developer who picks up the Jira ticket gets a sanitized summary with none of the nuance. They re-ask questions that were already answered in the doc. They miss edge cases that were discussed. The 2 hours of doc discussion was wasted because none of it transferred. Why does this persist in the first place? Google and Atlassian are competitors. Neither has incentive to build deep integration with the other. Google Docs comments are stored in a proprietary format with no public API for threaded comment export. Jira's API accepts markdown but not Google Docs comment metadata (resolved/unresolved, replies, anchored text). The integration gap exists because both companies benefit from lock-in.