-
Type:
Suggestion
-
Resolution: Incorrectly Filed
-
None
-
Component/s: Jira - Platform
-
None
Subject: Hide Rovo Dev panel on Jira issues while keeping other Rovo features enabled
Message:
Hello,
We’d like help adjusting how Rovo Dev appears in our Jira Cloud instance.
Context
- We want to keep using Rovo (search, Studio, etc.) and other AI capabilities.
- We do not want to use Rovo Dev.
- Under Atlassian Administration → Apps → AI settings → AI-enabled apps → Rovo Dev, we have turned Rovo Dev off.
- Despite this, the Rovo Dev panel still appears prominently in the middle of Jira issues in our project.
Example issue from our instance:
- Project: JKK – Jacki's Sandbox++
- Issue key: JKK-1040
- Issue type: Bug
- Status: Code Review
- Summary: “JKK creating Zendesk ticket test 5”
On that issue, there is a large Rovo Dev panel in the main content area of the work item (between the main description and the activity/comments), with options like “Generate code” / “Open in CLI”. We’ve attached a screenshot in the issue itself (image-20260218-214844.png), and that’s exactly the UI we want to remove.
What we’re asking for
Because of company policy and UI clutter concerns, we need:
- Either:
-
- A way to completely hide the Rovo Dev panel on Jira issues at an org/site level, while still keeping other Rovo features enabled,
or
- A way to completely hide the Rovo Dev panel on Jira issues at an org/site level, while still keeping other Rovo features enabled,
- The ability to manage the Rovo Dev panel via standard Jira configuration (e.g., issue layout / panel configuration) so we can remove it from the issue view.
In short:
- ✅ Keep Rovo (search, Studio, non‑Dev AI features).
- ❌ Do not allow Rovo Dev features to run (which we’ve already turned off).
- ❌ Do not show the “Rovo Dev” panel on our Jira work items at all.
Can you please confirm:
- Whether there is currently a supported way to hide this Rovo Dev panel from Jira issues?
- If not, can this be raised as a feature request or associated with an existing one so we can track it?
- If there is any workaround you recommend that does not require per‑user browser hacks, we’d be happy to try it.
Thank you!