points by godzillafarts 4 days ago | 0 comments
This doesn’t work in an org with stakeholders that don’t have access to the code base, I.e. most of the other company. You still need tickets, a way for stakeholders to follow, update, etc. those tickets, and a way to prioritize the tasks those tickets represent.
[–] Cthulhu_ 3 days ago
[–] trendschau 4 days ago
Totally agree that stakeholders need access, but I think that’s solvable with an interface layer on top of the repo rather than a reason to avoid the workflow.
[–] el_blargos 3 days ago
Or the other way around. An API for the robot to read tickets
But counterpoint, an AI / machines can talk to Jira and other ticket management systems just fine, they have REST APIs and MCP servers nowadays.