Rovo & Atlassian for Nonprofits Webinar Recap + Q&A

[#1]

This past week @Nikhil Kulkarni and @Farzad Yazdanparast hosted a Rovo & Atlassian Intelligence for Nonprofits webinar!

If you missed it, you can watch it on demand.

Thanks to those attending for asking lots of great questions. As promised, we will answer here the questions that we didn't get to in the session. 

What have you learnt about cleaning up documentation and old projects to ensure that Rovo's outputs are accurate?

So far, our conversations from customers confirm our belief that search relevance handles "noise" of old docs & work. To unpack a little bit, Rovo (like all GenAIs so far) has a limited "context window" (like an attention span). As such, we use Search as a mechanism to give Rovo the most useful content for any given task. Our Search layer weaves in multiple layers of relevancy checking, including user activity, that help to make sure Rovo is getting the most useful context. That being said, it never hurts to archive old versions of documents. 

Share in the thread if you have any thoughts on this from your experience!

Can Rovo create dashboards/reports later visible and sharable in Jira? Much of what I can think of is it's summarizing power and reportability.

We believe Rovo should help customers explore their own data. Right now, Rovo can help do that by converting natural language queries into JQL. However, we can imagine much more, including integrating our Analytics offering with Rovo for more generalized natural language to SQL. And even having Rovo help build dashboards and reports on the existing Jira capabilities. It will take some iteration before Rovo has those capabilities.

Are there any guardrails we can put on the agents users create?

Atlassian has implemented several guardrails for Rovo agents to prevent misuse and ensure safe operation. These include monitoring usage limits, enforcing acceptable use policies, and controlling access to information.

Also by aligning Rovo's permissions strongly to underlying products, including 3P,  Rovo makes it safe to spread agents far and wide. We are looking at some next steps we can take to delegate some of that control to product admins.

I have used Rovo to create tasks in a Jira project, but I couldn’t create a project with its complete workflow and status. Will this feature be added in future releases?

Actually, this can be possible now with Forge-based Agents! The limit in Chat or user-defined Agents is about Actions. Today, there's a subset of what you can already find as Actions from Automation. We're pulling those capabilities together in a common platform so eventually, everything available to Automations will be available to Rovo. Then, when we expand Automations, ideally to include 3P Connectors too, Rovo will get those Actions "automatically". Again, it will take some iteration before we fulfill that vision.

*Rovo as a product is rapidly evolving. These answers are up to date as of 1/27/2024

Have additional questions? Let us know in the thread.