# Code Review: Issues Migrator

**URL:** <https://meta.discourse.org/t/code-review-issues-migrator/167409>\
**Category:** Feature\
**Tags:** github\
**Created:** [16 oktober 2020 om 20:23 UTC](https://meta.discourse.org/t/code-review-issues-migrator/167409 "2020-10-16T20:23:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [18 oktober 2020 om 23:26 UTC](https://meta.discourse.org/t/code-review-issues-migrator/167409/2 "2020-10-18T23:26:09Z")

</div>

Oh, it sound like you are looking for a more permanent solution here. Have us regularly scan issue list and copy / close.

I guess workflow wise a good solution would be for you to tag stuff with `kind/support` and then if we see any new support issues we would close on GitHub, open on Discourse, add a post that links to Discourse.

There would be a bunch of work needed to make something like this happen, we would need to extend our Discourse ↔ GitHub plugin ([GitHub - discourse/discourse-github · GitHub](https://github.com/discourse/discourse-github)) we only do linkbacks now. But it is certainly feasable.

I don’t think this fits into the code review plugin though so re-tagging.

Is this the type of work you are looking at sponsoring? If so I can move this to our team inbox.

---

_[View the full topic](https://meta.discourse.org/t/code-review-issues-migrator/167409)._
