My colleagues' LLM assistants think that my LLM assistant leaves great JIRA comments.

haha! Funny enough I do have to tell the LLMs to leave concise comments.

I also don’t want to read too many unnecessary words.

Joking aside, I do believe we are moving into a era where we have LLMs write for each other and humans have a dedicated TL;DR. This includes code with a lot of comments or design styles that might seem obvious or stupid but can help another LLM.

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.

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.

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

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

Well I had half a mind to not tell them to see what they’d say, but I also was excited to show everyone so they can also be empowered with it.

One of them said “yeah I was wondering cuz you never write that much” - as a leader, I actually don’t set a good example of how to leave quality JIRA comments. And my view with all these things is that I have to lead by example, not by orders.

With the help of these kinds of tools, we can improve the quality of these comments. And I wouldn’t expect others to write them manually, more that I wanted to show that everyone’s use of JIRA on the team can improve.

Someone please shoot me if my PM ever gets this idea in his head of using LLM slop to spam tickets with en masse.

There's nothing I hate more than people sending me their AI messages, be it in a ticket or a PR or even on Slack. I'm forced to engage and spend effort on something it took them all of 3 seconds to generate without even proofreading what they're sending me says. The amount of times I've had to ask 11 clarifying questions because their message has 11 contradictions within itself is maddening to the highest degree.

The worst is when I call out one of these numerous contradictions, and the reply is "oh haha, stupid Claude :)", makes my blood boil and at the same time amazes me that someone has so little pride and respect for their fellow humans to do crap like that.

"I remember those days when we manually wrote comments"... - what were comments papa?

Sounds like your coworkers might be abusing things here.

I’m not remotely interested in throwing random slop in there.

In fact, we did try a year ago to have AI help write our tickets and it was very clear that they were AI generated. There was way too much nonsense in there that wasn’t relevant to our product.

So we don’t do that.

Notice they commented on the quantity, not the quality?

I don't think it's good leadership to unleash drivel on an organisation, have people waste time reading and perhaps replying to it, thinking it's something important and thoughtful coming from atonse.

Good thing you told them though, now they can ignore it.

It sure seems like the next evolution of Jira though. Designed to waste everyones time, picked by "leaders" that don't use it. Why not spam tickets with LLM drivel? They are perfect to pick up on all the inconsistency in the PM insanity driven custom designed workflow - and comment on it tagging a bunch of stray people seen in the ticket history, the universal exit hatch.

In another comment I mentioned that I ask for it to be concise.

Also, a lot of the kinds of comments are things like, when you combine a bunch of tickets, leaving comments on the cancelled tickets to show why they were cancelled.

In the past, that info simply wouldn’t be there.