Rovo Translation Tool – Still Supported?

[Manuel Nater]

Hi everyone,

As part of an international team, I’ve found the built-in Rovo translation tool extremely useful — it’s so convenient to access it through a simple smart label.

One of the biggest advantages for me is that I can create a complete article with files, pictures, and other content, then simply press the label button to have it all translated into one of the main languages while keep the formatting.

When I discovered this feature a few weeks ago, it worked perfectly, and I started using it more and more in my articles, also encouraging colleagues to do the same.

However, recently it stopped working. Whenever I activate the label, I repeatedly get the message:

“We did not receive an answer, please try again.”

Unfortunately, retrying doesn’t help — it just keeps failing.

Could someone please confirm whether this feature is here to stay?
Are we just experiencing temporary space or performance issues that will be improved as more resources are allocated to Rovo?
Or was this only a trial feature?

It would be great to know, as our team has started to rely on it quite heavily.

Thanks in advance for any clarification!

[Tomislav Tobijas · Accepted solution]

Hmm @Manuel Nater ,

I believe the AI translation feature is part of a phased rollout and is not (yet) guaranteed to be available in all environments at all times. But, from my knowledge, it's not just a trial feature.

I cannot say much more on this and I'll move the question to the Rovo forum group, but what you can also do is to reach out to Atlassian Support as they can check the current app version which is in your instance and also provide more info about the feature status in that version (or if there are any plans about it). 👀

Cheers,
Tobi

[Manuel Nater]

I think I have to rephrase my former statement. Previously I wasn´t using the Rovo translation tool but the label function. So by writing "/english" I could get a complete translation of the above written.

Then this stopped working or was very poorly executed.

Now this function is entirely gone. So when writing "/eng...." it is not even accepted anymore.

I then tried to prompt Rovo with something like "Please translate the above into english and included directly underneath the already written article"

The result is that it translating, even though with quite poor quality and it doesnt take in consideration the formatting from before.

So therefore this function is as useful as using an external translation tool, copy&paste into Confluence and reworking all formatting and pictures etc.

Will there be a more proper solution do this? I imagine I am not the only one which needs a multilingual approach on this?

[Tomislav Tobijas]

Ah, thanks for clarifying @Manuel Nater !

I can't say much as we write all our content in English, but I might give it a go on some of our materials that are in Croatian to see how it will behave (but yeah... I suspect it's not ideal 🫤)

As you mentioned /english action, I'm wondering if this will be somewhat related to the new Rovo Skills that they are introducing 🤔

I'll be honest, I haven't seen many questions and discussions about how Rovo handles translation, but you could browse this forum group. 👀

Btw, I've just moved this post to the Rovo group; forgot to do it earlier, so apologies!

Cheers,
Tobi