This is for tracking progress of our move to GitHub Issues.
Here's a copy of the task list from the developer chat:
I guess I should help with that.
I have begun work on this and will do a bit each day, will be done in 1 to 2 months.
I am assigning specific issues to specific people who know about them the most or have dealt with them lately. They can reassign if they do not want to work on the issue. I also recommend self-assigning issues if there is anything you can do. We can easily end up with thousands of issues from Mantis to GitHub and nobody is taking responsibility.
I have also started to look at Mantis issues and been testing and closing them as I go.
Thanks for helping out with this @ArranTuna 🙂
I've gone through the issues you've submitted (so many!) and updated them. It would be fantastic if you could use the issue template — it does take a little bit more time, but we should hopefully have it all done soon, esp. because we should have some more hands on deck for this!
All help is appreciated!
Also, the current plan is to ignore all the issues in the "Feature Request" project. (Don't migrate)
Ok will use issue template.
So I don't need to migrate any in the "New Feature Requests" project?
Thanks ❤️. No need to migrate any in the new feature requests project (unless you want a feature that's in there)
Oh also, if an issue is confirmed please add the issue to the "Backlog" milestone! cheers
I made this chrome extension to make migration easier: https://github.com/qaisjp/mantismigrate
Extension has been updated to automatically include a link back to the old mantis issue in the github issue
Extensions has now also been updated to make interface side-by-side. Let me know if you prefer the old style and I can make it a setting.
Most helpful comment
I have begun work on this and will do a bit each day, will be done in 1 to 2 months.