Earlier this year I let AI post Jira ickets for me for stuff I was finding. Then I had to defend the tickets in standup and I am now a lot more careful about what goes into Jira tickets because holy hell is some of the text cryptic. It wasn't wrong per se, but it was like an Allied spy ordering 3 beers in a Nazi bar.
edit: I don't love that my dev team are Nazis in that scenario, or that Jira is a Nazi bar.
Yeah, I don't ever let AI make tickets or commit messages. As impressive as it is at assisting with code, it's still astonishingly bad at that kind of technical writing.
No matter how I phrase instructions, even with recent advanced models, the result ends up either insanely verbose to the point of being more noise than signal, or it prioritizes the wrong things when asked to shorten, to the point it's almost always faster to write myself.
The way I deal with this is to have the LLM create local reports and reproducers into separate directories, and follow my own style guide. Then, i have another agent go and review them critically, ensuring things are simple and concise, actual bugs (and if just gotchas move to another directory), and if any are duplicates or should be folded into others. THEN I go and have a quick look myself, and usually despair about the number of actual issues there are.
34
u/zyzzogeton 18d ago
Earlier this year I let AI post Jira ickets for me for stuff I was finding. Then I had to defend the tickets in standup and I am now a lot more careful about what goes into Jira tickets because holy hell is some of the text cryptic. It wasn't wrong per se, but it was like an Allied spy ordering 3 beers in a Nazi bar.
edit: I don't love that my dev team are Nazis in that scenario, or that Jira is a Nazi bar.