i'm just going to throw out a few questions asking if features i wish these kinds of systems had are in here. maybe they are, and if they aren't, hopefully it's helpful!
what is the workflow like for going from a commit id (ala git-blame) to all available discussion and context around that change?
is there any sort of unified search through history that shows both changes and all discussion/context around them? (pull requests, kanban cards, related issues and prs, design docs/sketches/etc, slack threads)
is there any workflow/smarts for detecting recurring issues/bugs/fixes?
i used to ask "can you drive most of it by email" ... i guess these days it's "can you drive most of it by chat integration?"
Thats something we're working on i.e most of our R&D goes here, we've been building up capacity on getting contextual data from the commits/PR's and possibly from slack too and then surfacing it as meta data as a first step. For example being able to identify questions, solutions, possible additions to documentation.
The aim is to eventually pass on that data or use it for smarter inference like catching duplicates, bug frequency, reintroduction of code and possibly identifying tech debt. Our vision has been to go ticketless, while we're supplying the tooling to make those tickets today, in the future contextual information from different systems could provide enough context to do that work.
what is the workflow like for going from a commit id (ala git-blame) to all available discussion and context around that change?
is there any sort of unified search through history that shows both changes and all discussion/context around them? (pull requests, kanban cards, related issues and prs, design docs/sketches/etc, slack threads)
is there any workflow/smarts for detecting recurring issues/bugs/fixes?
i used to ask "can you drive most of it by email" ... i guess these days it's "can you drive most of it by chat integration?"