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; } } }

Is Rovo Becoming the First Tool We Open Instead of Jira?

Yashodip Jadhav

When I first started using Rovo, I treated it as just another AI feature inside Atlassian.

But over time, I noticed something interesting.

Instead of opening multiple Jira tickets, Confluence pages, and project boards to find information, I often start with Rovo and ask a question first.

It doesn't replace Jira or Confluence, but it changes how I interact with them. Rather than searching manually, I can get a quick summary, understand context faster, and decide where I need to go next.

For me, the biggest value isn't generating content it's reducing the time spent looking for information.

I'm curious whether others are seeing the same shift.

Are you using Rovo mainly as a chatbot, or has it become your starting point for finding information across Atlassian tools?

Comments

Tom Hudgins

Maybe it's just me/our environment but Rovo is so incredibly inconsistent in it's abilty to do things that I basically never use it. It's just about the dumbest AI that I've used so far.

jh074626

@Yashodip Jadhav , that's exactly how I use Rovo. In fact, immediately before I opened this email, I asked one of my developers to check for a Jira ticket to unschedule a concurrent program, and that's how I expect him to look for it.

I'm pretty good with JQL, but for a search like that, JQL isn't worth the time.

Now, we've not used Rovo for any kind of automation, at least not yet. But given time, it is something I'd like to look at amongst the myriad other things I'd like to look at. 😁

Chris Bezile

I agree 100%. Rovo is currently useless IMO. Another agent using the Atlassian MCP provides much better results.

Chris Bezile

The search bar in Jira and Confluence work better than Rovo. I don't use Rovo for anything due it's glaring lack of consistency and ability to do anything meaningful.

Yashodip Jadhav

Thanks for your experience @Chris Bezile ,but the ROVO is just comes in a market, atlassin trying to do it better everyday,may be in after a year we love to use ROVO than now till then just use it and try different different ways,if found anything on it about improvement the Atlassin doors are open for us we can gave them Suggestions

Yashodip Jadhav

Thanks for sharing your experience @jh074626

Yashodip Jadhav

@Tom Hudgins Agreed with you but at the end it is a machine it can make mistakes, Atlassin everyday take a Suggestions and making improvement day by day in ROVO may be in some days We love to use ROVO btw thanks for sharing your experience ❤️

thiago_miranda_ea0bzj

I haven’t reached the point of using Rovo as my starting point yet, though that might just be out of habit since I'm used to looking for information myself.

However, in my organization, we frequently use the Rovo chat to look up specific information or to handle simple tasks, like improving ticket descriptions or suggesting subtasks.

On top of that, we are already using at least two Rovo Agents that really help with our workflow (one that assists with the initial triage of incidents, and another that helps during the ticket review stage).

Becker_ Rene

We (= ~0,5%) use it to find something when we are not sure where to find it or if we have something in the back of our head and am not sure how to find it otherwise but using semantics.

Although Rovo does a halfway decent job, almost nobody uses it. That's mainly because of it being hard to find/access/use where it is needed (for example inside the page editor in Confluence) but placed at places where it is most annoying and getting on people's nerves (example above comments in Jira Service where it pushes comments down, overlaying buttons in products, reminding about it being there , suggesting stuff etc.).

Using it for productive tasks, like translating a page without editor, creating a page, moving something around etc. it shows clear limitations / token limits (it seems). Using it in Automations also dows not keep to its promise (what are we to do with a 10.000 char limit?).

All in all, our people are frustraded with it, hence ignore it as good as possible and rather use Copilot, ChatGPT, DeepL etc. (which isn't a great solution either ...)

With pushing Rovo in every product on all users, pushback grows even stronger each time. Just like CoPilot -> The more Microsoft pushes, the harder people push back on it.

On a personal note: Rovo is the reason I cannot remove shadow instances on my tenant - that does not help either.

So all in all: wasted potential.

PS: We tried to inform people of Rovo's capabilities, even run a "campaign" - people still opt to use other LLM.

---

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

rovo-atlassian-intelligence

atlassian

rovo