Does Rovo need Jira Admin training?

[Rebekka Heilmann _viadee_]

I made an interesting discovery playing around with Rovo now that we finally have it on our productive site as well.

I simply asked "Show me all my open issues", feeling like that would be something a lot of users may ask for.

Looks fine, you say? Look a little closer.

Yep, that's right. Rovo shows me all my issues (so far so good) that are not in the Status "Closed". Insert Alarm sound here.

One of the first things you learn as a Jira Admin is, that you should never query statuses but always the resolution, just like the standard filter "My open issues" does as well. Now, of course I could ask Rovo for my *unresolved* issues. But what user would do that?

So my question is: Does Rovo need to study some of the Atlassian University courses? ;)

[Jack Brickey · Accepted solution]

Ha! Indeed it seems so. I guess normal language only goes so far. ;-)

[Jack Brickey]

BTW, rather than Resolution I often use "statuscategory != done" since sometimes projects don't set the Resolution. :-(

[Dr Valeri Colon _Connect Centric_]

@Jack Brickey in da' house. Now you gotta stay awhile.

[Dr Valeri Colon _Connect Centric_]

Great catch @Rebekka Heilmann _viadee_! You’re right—using status != Closed instead of resolution = Unresolved (or statusCategory != Done) can lead to misleading results. This is a great example of why humans as reviewers are essential in AI workflows.

It’s not quite ready for Atlassian Learning, at 1 years old Rovo is still in diapers 😄, but giving feedback via thumbs-down helps it improve. And @Jack Brickey solid tip on statusCategory != Done—super useful when Resolution isn’t set!