nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Userscripts to disable Rovo?

Nick Hatch

Hi,

Like many other users, I find the rovo feature placement, logos, and popups distracting and obnoxious.

Since Atlassian gives end-users and administrators very little control over these features, does anyone in the community have any tips on good UserScripts to block and remove these features within the browser? Seems obvious that Atlassian has made their user-hostile decisions, and doesn't want to give people control over this.

Accepted answers

Aaron Pavez _ServiceRocket_

Hi @Nick Hatch

You could try creating your own Chrome extension for example.

Or use U block origin to hide elements in the page.

Or you could try this: (I dont know how safe is this BTW)

https://github.com/birgit-babbel/chrome-extensions-jira-customise

Regards

All comments

Aaron Pavez _ServiceRocket_

Hi @Nick Hatch

You could try creating your own Chrome extension for example.

Or use U block origin to hide elements in the page.

Or you could try this: (I dont know how safe is this BTW)

https://github.com/birgit-babbel/chrome-extensions-jira-customise

Regards

Dr Valeri Colon (Connect Centric)

@Nick Hatch browser extensions, uBlock filters, or custom userscripts can hide Rovo UI elements locally, but I’d be careful with this approach. It may break when Atlassian changes the UI and could create security or support concerns, especially in managed environments. For org-wide control, the safer path is still Atlassian admin settings for Rovo/AI access, even if they don’t remove every visual element today.

Rob Bl

This problem with this "solution" is that other people in the company may like having AI assistance. The fact that Atlassian chose to make control over Rovo an admin-level setting just goes to show how little Atlassian cares about the user experience. Because other people in my organization like to use AI, those of us who have no use for it, and in fact hate it, are stuck with Rovo getting in the way dozens of times a day. Remember Clippy in Mircosoft Office from the ’90s? That's what it's like having to put up with Rovo.

It is so blatantly obvious that AI use is a personal preference, and yet Atlassian chose to ignore users in favor of giving this power to admins.

It's just like how users have no control over the date format in Atlassian. Everyone in an organization is forced to use whatever date format the admin has chosen, regardless of the user's region or personal preference. Atlassian just doesn't care about the experience for the end users.