Not a good move. "Issues" is THE way to track Tech debt related to a repo. It is also empowering for non-dev users of the repo - SDETs, testers, PMs to suggest changes and best practices. Gitlab has this and this is something I have ALWAYS used to track suggestions for improvements and track tech debt - i.e. missing tests, missing features etc.
How will I communicate things like - this repo needs a Changelog, tests need a separate folder, need to move package a to version x.y.z .... Opening tickets in JIRA, putting it in a backlog, etc. will be giving this to non-technical folks who may not judge the items with the same urgency/consideration.
52 comments