[mananaysiempre]

Thus far I’ve found Jira’s AI features to be basically nonsensical (and they’re constantly annoying me with downright childish amounts of bling, like if you asked a five-year-old to design a product box). So that seems perfectly in character.

All right, there’s a related-tickets feature that could have been great (witness the related-questions feature on Stack Overflow’s ask page, widely acknowledged to search better than the site’s actual search). It’s just no good at what it’s sup posed to do.

[sevensor]

> Jira’s AI features to be basically nonsensical

Unlike its other features?

[mananaysiempre]

I mean. Like. It files tickets. Closes them. Links them. Accepts comments. Sends email to me when all that stuff happens. I can make it send email to others too. All that seems fine? The web UI of the hosted version runs like absolute ass, and its inability to preserve a ticket being created when I accidentally close the tab is downright offensive, or at least what comes out of my mouth when I experience that definitely is. But otherwise fine? ( /s, a bit)

I haven’t had to use the more egregious stuff like time tracking, as you can tell. I think one of our projects has a kanban board somewhere, but I’m not a release manager so I’m mostly living in happy ignorance of what’s on it. It’s not a large outfit, thankfully.

[lmm]

> Closes them.

Or resolves them. Or sometimes both, or sometimes neither, and maybe you can undo one but not the other. I wouldn't say it manages to make sense with that piece of functionality.

[Esophagus4]

Agreed. Though I will say using the AI to JQL tool is nice.

And I use Confluence’s AI pretty often.

[blackqueeriroh]

Completely disagree. Rovo has been an incredible game changer for us. It speeds up work by like 30% and brings context to information rapidly.