Rovo floaty blocks screen information

Hi @randy 

You could try one of the following workarounds:

1. Custom CSS / Style Extensions (Quickest Personal Fix)
   If you use a browser extension like Stylebot, Stylus, or uBlock Origin, you can hide or reposition the floating widget element entirely on Jira board views:
   
   Hide element CSS rule:

   • [data-testid*="rovo-floating-launcher"], 
     [aria-label*="Rovo"] { 
     display: none !important; 
     }
     

2. Submit Product Feedback directly to Atlassian UI Teams

   • Select your Profile Avatar in the top navigation bar → Give feedback (or Feedback under settings).

   • Flag the floating button overlap specifically on Kanban/Scrum Board Card Views so the design team can improve element positioning or add a toggle to minimize floating launchers.

3. Check with your Site/Organization Administrator

   • If your team manages Rovo access via Atlassian Administration (id.atlassian.com / admin.atlassian.com), admins can configure Rovo surface displays or agent widget positioning for specific Jira spaces/help centers.

Hope this helps & resolves your issue. 🙂

Thanks,
Anwesha

Hi Randy,

I can see why this is frustrating, especially if the floating launcher is covering card content on a Kanban board.

At the moment, I’m not aware of a native Jira setting that lets users reposition or disable that specific floating Rovo launcher while keeping Rovo available elsewhere in the UI.

Since you already have access to Rovo from the main navigation, this looks more like a product/UI design issue than a board configuration issue.

A couple of practical things I’d suggest:

use Give feedback from your Atlassian profile and include a screenshot showing exactly which card elements are being covered;
mention that the launcher is duplicating an existing Rovo entry point and forcing additional horizontal/vertical scrolling;
if this affects several users on your site, have multiple users submit the same feedback so Atlassian can see the impact more clearly.

I would avoid relying on custom CSS or browser extensions as a long-term fix, especially in a managed corporate environment, because those can break when Atlassian changes the DOM/UI.

If Atlassian adds a supported toggle to hide or minimize the launcher, that would be the cleanest solution here.

You’re not imagining the UX issue — the button is clearly occupying space that can interfere with board content.

That would be my preferred route for now.