[throwaway892238]

Yeah, what they're asking for needs to be an app / integration / plugin that ties different solutions together. A kitchen sink approach will forever be mired in gigantic codebases that a single group or company can't coherently maintain [at a reasonable time or cost], and a marketplace of solutions is better able to evolve. We need more simple and specific tools that don't do much, but can be combined with other simple specific tools.

Take branching models for example. Why do we have different "branching models" that work certain ways? Firstly because somebody built a tool that works a certain way (Git) and people need to figure out how to use it. Secondly because how you use it has a direct effect on other things, so you need some coherent model for how your group will use it. And thirdly because there's a few specific ways of using the tool, so we write those down and give it a name. Nobody set out to design these branching models, they just evolved as people started using the tool in different ways.

The same should (and kinda does) happen with project management, time tracking, issue/bug/work tracking, documentation, incident response, budgeting, etc. But mostly it's within one ecosystem (Atlassian's) or another. It should really be more general, and it should be easier to integrate different solutions and build on top, and from there new standard patterns can emerge such that we don't have to be stuck into one ecosystem.