I’m looking to switch management of a GitHub organization over to Plane. We make heavy use of GitHub issues. I see from the docs that tagging existing issues with the label Plane synchronizes over to Plane. However when I tried this, it only synchronized the issue title and description and none of the historical comments. This means that it is effectively impossible to resume work from this purely within Plane; you have to go back to GitHub to see the full discussion. And this makes the whole migration harder.
Is there any way around this? And if not, please can it be fixed to synchronize all comments?
It seems there wasn’t, so I have concocted the following workaround:
- Put sync into unidirectional mode
- Add the
Plane label to the GH issues I want to import, and wait for them to import. The comments will be missing.
- Run a script I wrote which imports all the comments into the corresponding Plane work items.
- Re-enable bi-directional mode.
If anyone is interested, I’m happy to share my script.
@aspiers, thanks for sharing your workaround and the script. This will definitely be useful to other users importing issues and comments from GitHub. Appreciate the contribution 
.
it already is. thank you so much for doing this, @aspiers. 
You’re welcome. It would be great if the official GitHub integration solved this correctly so that we don’t have to write custom scripts to work around the gaps.
Unfortunately I have found several other bugs with the official integration, and have filed GitHub issues for each. Here is an overall meta-issue which indexes the others: Plane→GitHub sync silently overwrites GitHub bodies with corrupted markdown · Issue #9077 · makeplane/plane · GitHub
Due to these bugs it’s not really usable in its current form. This is currently blocking the migration of our project to Plane, and I’m struggling to see a good way to proceed other than rewriting the entire integration from scratch myself, which would obviously be far from ideal.
Any advice hugely appreciated. If these can be fixed quickly (or at least the most painful ones), then we can maybe wait a short while for that. However if they’re unlikely to be fixed any time soon, it would be really helpful to know up front so we can plan accordingly. Thanks a lot!
BTW I notice that my most recent bug reports filed above don’t have labels, and it looks like this means they don’t have the plane label either and so haven’t been synced to your Plane instance. Sorry for the extra trouble, but I don’t have permissions to add labels so it would be great if someone who does could take care of this.
