> Having to create issues-only repositories seems like a sign that one may be using the wrong tool. JIRA is a pile of bolted-on features, and no one has ever m

> Having to create issues-only repositories seems like a sign that one may be using the wrong tool. JIRA is a pile of bolted-on features, and no one has ever measured what is essential to project management, so this point strikes me as sort of an ad populum than an argument that JIRA or whatever is more fit for some PM task than Github Issues. This is what kills me about software project management, at least in Enterprise where I work: its about people consistently communicating to one another; that's it, lest there's something else we can extract as somehow more primordial. Somehow people consistently communicating over a topic has been reified to the point that we mistake the reified things for the thing-in-itself.