Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Rovo should understand Atlassian's own terminology

I've been trying to build-out and use Rovo agents and it's quite annoying that it regularly tries to correct me for using the term "space" in reference to what was previously known as a "project". This terminology transition has been so poorly implemented that Atlassian's own tools don't know about it.

I asked Rovo to find errors in some documentation and this came back.

Terminology Errors

  1. "Jira space" / "space" used instead of "project" — Throughout the page, Jira projects are referred to as "spaces" (e.g., "Jira activity for any space," "Non-IT Spaces," "Summarizing Jira activity for any space"). In Jira, these are projects with project keys. "Spaces" is Confluence terminology. This is pervasive and could confuse readers who are newer to the tools.

It's already tough enough to explain to users why you have to use "project = ABC" when trying to query a Jira Space, but now Rovo is telling users to use the old terminology after we've been trying to teach people the correct new terms.

End rant.

2 comments

Joanna Madden
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 8, 2026

This is an LLM thing in general. Copilot, ChatGPT, Gemini all have these moments as well where they don't know their new terminology or integrated products. It is frustrating - I'm with you there, but it's a new normal. In a perfect world it would know both old and new, but even a well trained model won't handle that with consistency - it's just not how they work. 

Like # people like this
Kris Klima _K15t_
Community Champion
May 8, 2026

I had Rovo refering to a Confluence 'instance'. Several times. Despite the fact that the source used 'site'.

(Among other things like suggesting changes to a section that's not there...)

In general terms, it may be a 'new normal' (as @Joanna Madden writes), the problem is that this approach constitutes a massive deterioration of expectations on our part, as users, about what a paid-for product can do reliably. Which is quite astonoshing especially in the context of how that product is presented. In other words, there's discrepancy among hype / expectations / reality.

Knowledge tool gets the essentials wrong. Dictionary shows a different definition of the same word to different users or on a different day, your car suddenly showing kilometers instead of miles because you said something in German.

Thanks for listening, Saturday Philosophy Morning with Kris returns next week :) 

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events