design notes

[naturallymitchell]

ideal issue tracker

https://news.ycombinator.com/item?id=18885942
Ask HN: What would your ideal issue tracker look like?

it'd support local development and network remote instances for online and offline use

it'd have stakeholder management tools built into its project management tools, ie changelogs and release notes following through from planning phases

it's have auditing tools and model-driven architecture tools to check plans against principles (related to automated responses to same types of questions and automatic step through documentation phases from changes)

it'd have tools for participatory innovation builtin, ie users reviewing releases, plans, and designs

it'd primarily follow the principles of change management, so "bug reports" and "feature requests" would be abstracted

it'd support change management of the software itself, driven against the model of the software design it follows

it'd have chat channel integration for seemless planning session data integrity

it'd have vcs integration

https://en.wikipedia.org/wiki/Change_management_(engineering)

https://en.wikipedia.org/wiki/Stakeholder_management

~~

this looks very good https://www.aha.io/