Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Rovo
  • Questions
  • Rovo Chat automatically converts plain text into entity mention tokens - no way to prevent this.

Rovo Chat automatically converts plain text into entity mention tokens - no way to prevent this.

Sergey Osherov
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!
July 7, 2026

Description:

When typing certain words in the Rovo Chat input field — such as "Jira", "Projects", or "Confluence" — the editor automatically converts them into inline entity mention tokens (colored pills with icons). This happens:

  • Instantly, without showing any autocomplete dropdown or popup to dismiss

  • Without any floating toolbar to revert the conversion

  • Ctrl+Z and Esc do not work to undo the conversion

This is disruptive when trying to write plain text messages that reference these products or concepts without linking to specific entities.

Steps to reproduce:

  1. Open Rovo Chat

  2. Type a word that matches a known Atlassian entity (e.g., "Jira", "Projects", "Confluence")

  3. The word is automatically converted into a colored entity token with an icon

Expected behavior:

  • The text should remain as plain text unless the user explicitly selects an entity from an autocomplete dropdown

  • Or: provide a way to dismiss/revert the conversion (Esc, Ctrl+Z, or a floating toolbar)

Environment:

  • Rovo Chat (accessed via Atlassian Home)

  • Not occurring in the Confluence page editor

Request:
Please either:

  1. Show an autocomplete dropdown that requires explicit user selection before converting, or

  2. Provide a reliable way to dismiss/undo the conversion (Esc/Ctrl+Z), or

  3. Add a user preference to disable automatic entity token insertion

1 answer

1 vote
Germán Morales _ Hiera
Atlassian Partner
July 7, 2026

@Sergey Osherov , there's no user or admin setting that controls this, and I couldn't find an existing report for it on the public tracker either, so this looks like an unreported bug in Rovo Chat's editor rather than documented behavior with a workaround.

Worth filing it directly on the ROVO project at jira.atlassian.com rather than waiting here, that's the public tracker Atlassian's Rovo team actually triages, and other people hitting the same thing can vote and watch it once it exists.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events