I've been using GitHub Issues (and their new Projects feature) more and more. It's far from perfect, but I really value the colocation of code + task management

I've been using GitHub Issues (and their new Projects feature) more and more. It's far from perfect, but I really value the colocation of code + task management it allows. I like being able to reference issues/PRs by # in markdown comments - it feels more natural to leave "breadcrumbs" this way so that others can follow the chain of events when trying to piece something together. One thing we've done internally, for all tasks that aren't tied to a repo (because GitHub issues must belong to a repo), we created an "internal" repo that's a catchall for tasks not necessarily tied to a codebase. The Projects view then let's us plan work across multiple codebases and this "non-codebase" repo