[eknkc]

Why use JIRA at this point then?

Can’t we point an LLM to a sqlite db and tell it to treat it as an issue tracking db and have everyone do the same.

The service (jira) would materialize inside the LLMs then.

Why even use abstractions like tickets etc. Ask LLM what to do.

[zoogeny]

JIRA is more than just ticket management for most big orgs. It provides a reporting interface for business with long-term planning capabilities. A lot of the annoying things that devs have to do in JIRA is often there to make those functions more valuable. In other cases it is a compliance thing as well. Some certifications necessary for enterprise sales require audit trails for all code changes, from the bug report to the code commit. JIRA provides the integration and reporting necessary for that.

Unless you can provide the same visibility, long-term planning features and compliance aspects of JIRA on top of you sqlite db, you won't compete with JIRA. But if you do add those things on top of SQLite and LLMs, you probably have a solid business idea. But you'd first need to understand JIRA well enough to know why they are there in the first place.

[falcor84]

Exactly, applying the principle of Chesterton's Fence [0].

[0] https://en.wikipedia.org/w/index.php?title=Wikipedia:FENCE