Migrating Issue Management to GitHub

[qgib]

Author Name: D M (D M)
Original Redmine Issue: 18168

Redmine category:unknown

---

Issue and feature management is already done in GitHub for other QGIS repositories (e.g. QGIS-Documentation).
Given that GitHub is already used for hosting the QGIS repository, I think it would make it easier to reference, open and close issues directly in GitHub.
It looks like there are migration docs and tools out there to do this automatically (e.g. https://blogs.harvard.edu/rprasad/2014/07/10/moving-from-redmine-to-github-issues/).

[qgib]

Author Name: Richard Duivenvoorde (@rduivenvoorde)

---

Note that we are discussion about this already for some long time.

See:

https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018#moving-the-qgis-bug-tracker-away-from-redmine

and

https://github.com/qgis/QGIS/wiki/QGISbugtracker

[qgib]

Author Name: Richard Duivenvoorde (@rduivenvoorde)

---

Will close this as this is not about QGIS itself, but about the infrastructure to use.

---

• status_id was changed from Open to Closed

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• resolution was changed from to invalid

[qgib]

Author Name: D M (D M)

---

Thanks -- for completeness I'd like to address the following points made in the page you linked to:

nobody was able to mass insert existing issues OR think of moving from Redmine to Github issues

have to come up with a plan to either export (some) tickets from redmine OR decide to start with a clean (3.0) sheet??

redmine2github (https://blogs.harvard.edu/rprasad/2014/07/10/moving-from-redmine-to-github-issues/) can help.

closed system

I am not really sure what is meant by this.

have to come up with a plan to handle 'tagging'/tagging system of issues to be able to search tickets? I started with some idea in 2015: https://github.com/rduivenvoorde/temp/issues

Handling, searching, assignment of issue is, in general, much simpler if done correctly. See, for example, how much larger projects handle issues on GitHub: https://github.com/Microsoft/vscode/issues