Feature request #18168
Migrating Issue Management to GitHub
|Pull Request or Patch supplied:||No||Resolution:||invalid|
|Easy fix?:||No||Copied to github as #:||26059|
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/).
#1 Updated by Richard Duivenvoorde about 5 years ago
Note that we are discussion about this already for some long time.
#2 Updated by Richard Duivenvoorde about 5 years ago
- Status changed from Open to Closed
Will close this as this is not about QGIS itself, but about the infrastructure to use.
#3 Updated by Giovanni Manghi about 5 years ago
- Resolution set to invalid
#4 Updated by D M about 5 years ago
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.
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