Rebekka Heilmann (viadee) Community Champion

I regularly use Rovo to find information that I don't know exist. Usually I've used search to find stuff I know is there. But now Rovo surfaces information for me, I only know vaguely about. Such a time saver! I also use Rovo to fact check my KB articles - that's the great thing about Rovo being connected to the Atlassian…

List and All work FINALLY merged! I've been saying this in my enablement sessions for over a year now "expect these two to become one". Also very exciting Update for Loom - still trying to convince people of the value it could bring to a lot of our teams. This one is certainly a time saver that could help my argument.

I've never mentioned an archiving strategy to be fair. I see this as a temporary bridge between Cloud and DC while the company is working on the Transformation. But: temporary could mean a few years when dual licensing is long expired. The articles are not helpful as they don't answer my question explicitly.

Hi @Teal Wilkes - welcome to the Community! Atlassian-hosted LLMs are available to Enterprise customers on request: Atlassian-hosted LLMs | Atlassian Support There are still some limitations to it and mainly covers Jira Software and Confluence, but they are working on improving that.

@Olli Suokas 3rd parties oftentimes don't know about Atlassian Service Accounts and still use the term for what I would now call "Technical user". Some integrations still don't work with Service Accounts and require a regular user account instead. A real Service Account can't be granted Jira Administrator permissions (yet…

I have created an Agent that validates if People have uploaded the correct Rovo Fundamentals certificate so we can grant them Rovo Agent Permissions automatically. The knowledge check is already automated through JSM Forms + Automation. Rovo takes the attachment and checks if the name matches the reporter and the…

Still the same issue as reported in 2018 then. Thanks for confirming! Nah, not tried that as i hoped the issue was elsewhere. Not going to add Web requests to a simple Automation in this case so will go a different route than issue properties then.

Still the same issue as reported in 2018 then. Thanks for confirming!

I @Kanwar Robinson - welcome to the Community, don't know for sure, but from the documentation and how Atlassian works elsewhere, MCP rate limits are separate from API rate limits. So internal API calls are not counted when invoked by the official Atlassian MCP.

Celebrating all Jira Admins, who are becoming so much more than "just" Jira Admins these days. Celebrating the Modern Atlassian Admin: A Poetry Slam Reflection

Hey @Tori Kaulins interesting Tip you are sharing. Could we not use Rovo's explicit memory for general rules we like Rovo to follow for every session?

That's what the instructions are for. You provide the right knowledge, add understanding about relations between it and give the Agent a task. What else do you need?

Rovo Sub-Agents already work independently and can be consolidated by the main Agent. You could also concatenate Agents in Automations.

Rovo has memory and learns over time: What is Rovo memory management? | Rovo | Atlassian Support

You can prompt Rovo to find conflicts and contradictions. You could also set this up in Rovo's memories. Note: This is not really a Question but rather a discussion, best suited for the discussion forum: Atlassian AI & Rovo - Atlassian Community

I agree that AI Adoption cannot be purely based on Credits used or people reached. For Agents, you can already see thumbs up/down ratings and only Agents that are genuinely helpful should stay active. That way, the number of Agents eventually will reflect successful implementation rather than just Agents created. Note:…

This is actually very outdated. Atlassian Intelligence does not exist anymore. There are some relicts in the UI that still call it Atlassian Intelligence but it is all Rovo now. Rovo always uses context knowledge.

Hi @植木　智子 welcome to the Community. I've tried to translate your question but not sure if I understood correctly. Rovo Agents will not show the correct context when triggered via Chat? This may depend on Agent's knowledge access and context is also not always shown. There's been some bugs around this. Once you delete the…

My recent observations is that with the Read Images skill that now works well. PDFs work, as long as there is a full text layer. PDFs with image only will not work and Rovo Agents will hallucinates the most random things.

I did win dive holidays about 10 years ago but my absolute best finds were in a few charity shops in Scotland last year: In Oban, I went into a shop and couldn't believe my eyes: I got a print from an artist I actually know personally for 5 instead of 80 gbp. It was still wrapped and untouched! Always thought about getting…

Hey guys, we are encountering issues with using MCP with Service Account Tokens. SA Tokens need to be scoped, but MCP seems to require different scopes than API does. Will required scopes for tools like TWG access be added eventually? Is there any work around?

I would have thought a delete is a delete. But with Atlassian, anything is possible.

Hi @Krishna Modem what exactly is your problem? What do you mean by "Old" Confluence source?

Hi @Eric J Trumbull Rovo Connectors generally retain data for 30 days after disconnecting them so I'd guess that it also retains data that is deleted in the connected App for 30 days. From my understanding, permissions are updated more timely - not quite immediately but I think it's only a few minutes. I don't have any…

My 2 cents: I don't think Atlassian will deliver the user level control to Standard/Premium any time soon as they WANT us to consume more credits than we have available to push for Collections or additional credit purchases.

I second @Jason Krewson and @Arkadiusz Wroblewski I have tried a workaround with using IP Whitelisting on the Rovo App. That sort of works, if you can give the whitelisted users access via the whitelisted IP. But: Everyone will still see Rovo in the UI, but will get an error message in the Chat/as soon as they invoke any…

Hi @Jeffrey Bistrong this is down to Studio Automation covering different Use Cases than Jira/Confluence Automation, according to the Atlassian Studio Team. Studio Automation is open to all Users (depending on Studio permission) regardless of Space Admin permissions. It's meant for automating personal Agents or Team-level…

Hi @Andrea Del Pilar Porras Rodríguez - welcome to the Community, plain Rovo Chat can be configured via the icons on the bottom. You can uncheck connected Apps there. You cannot (de-)select single Spaces. You can however specify what you want to search in the prompt. This is not a garantuee that Rovo is not looking…

Hey @Andrew Zimmerman a bit late to the discussion but here is how we handle it: * A section in the usage policy that only allows the Agent owner to use their own Agent in their own Automation. Nobody else is allowed to use it. * Jira Automation and Rovo Agent creation each require separate certification and approvals…