Jensen Fleming Atlassian Team

@Rimantas Andrulevičius Apologies, replaces was probably the wrong word there, it is a separate option for the Portal, you can choose VSA or Rovo for answering helpseekers. Rovo is not available for non-licensed users, as of now -- but keep an eye on https://jira.atlassian.com/browse/ROVO-119 -- we will be updating this…

Thought I'd ping our top Rovo Champs from last month. Hopefully helpful intel for you all. Let us know if you have any questions/feedback! @Rebekka Heilmann _viadee_ @Tomislav Tobijas @Nikola Perisic @Dr Valeri Colon _Connect Centric_ 

Please email me at jfleming2@atlassian.net with your domain. 

Were getting through our final small bugs. Hopefully out EOD or tomorrow. If you send me your domain, I can add your site to the feature flags so you can use it now. 

Hi everyone, we have a fix coming out for this ASAP! ETA is early next week, just going through testing. Please follow this JAC ticket: https://jira.atlassian.com/browse/ROVO-229

Hey @田中優貴 -- The "users and permissions" that currently exist on Agents, is for "editing/managing" the agent, not for "using" the agent. Currently, anyone with access to Rovo/AI in your site, can use any agent. There is no blocker here. We will be adding "who can use this agent" permission in the near future. It will…

@Gary Spross Glad its working now!

@Gary Spross -- that sounds odd! Are you sure you are in the same site in browser that you connected to Slack? I think opening up a support ticket here would be our best path to resolution. 

@Alex Stillings please watch and vote for this feature request :) https://jira.atlassian.com/browse/ROVO-234

@Josh AgentResponse will use the value from the result of the previous node. If you want to save that response for later, you can save it as variable via `Create Variable` action.

@Romain Delmotte Can you confirm that you are using an Agent? This does not show up in a non-agent Chat. Also please make sure it is on a message response from an Agent. If you still aren't seeing it, can you send a screenshot to us (and preferably open a support ticket).

Hey @Ryan Boyd -- this should be resolved. Can you try again? 

Can you try clicking "edit details" and submitting instead of the confirmation button and letting me know if that shows required fields? This issue should be fixed early next week for required fields (if that is the cause here). 

TY! Looking. Curious do you have any required fields on this ticket? We have a fix coming for that today. 

@Adrian May Coming soon :) We're kicking off a work stream now on "who can use this Agent" Ticket here for tracking: https://jira.atlassian.com/browse/ROVO-142

Hi @Rebekka Heilmann _viadee_ thank you for pinging me. I'm unable to reproduce this. Are you still seeing the error? Can you both also send me your support ticket links? Can you also try creating a ticket without an agent, just via Rovo Chat directly?

@Luísa Ribeiro it's live! https://www.youtube.com/watch?v=GbNbzDL5LJk

Thanks for linking the JAC ticket and tagging me @Josh I just updated the ticket -- we are kicking that stream off now, I'm very excited for it (especially necessary with the addition of collaborators). One other related thing that we are building right now is user uploaded Eval Sets, so you will be able to test quality on…

Hey builders! Check out this page on how to write great triggers for your scenarios :) https://community.atlassian.com/forums/Rovo-articles/Write-Triggers-Like-a-Pro-Your-Guide-to-Crafting-Great-Scenario/ba-p/3121842

@Rebekka Heilmann _viadee_ @Nikola Perisic @Laura Campbell -- Here is a feature request ticket to vote on! https://jira.atlassian.com/browse/ROVO-289 We'd love to support it, just never was high enough priority to put it above something else. Will keep an eye on the ticket to gauge interest :) Cheers! Jensen

@Bryan Kenny Org admins can transfer ownership to themselves (or someone else) if an agent creator leaves. They also have the ability to delete any agent :) 

Hey @Rebekka Heilmann _viadee_ -- in the next 1-2 weeks, you’ll be able to assign a “team sponsor” to an agent (displayed as “by...XXX”). This will make it clear which team the agent is associated with—for example, the IT Support Team owning the IT Assistant agent. Please note: assigning a team sponsor does not grant…

Hey @Rebekka Heilmann _viadee_, Thank you for your note, and apologies for missing it earlier! I completely understand your interest in being able to swap out models—this is something we are considering, but we haven't heard a ton of interest in this (yet). Prior to this update, agents were closely tied to the same backend…

Hi Friends! I'm a Product Manager on the Rovo team and wanted to let y'all know that we are actively working on bringing the Rovo experiance into Slack via a Slack app. I've marked this suggestion as in progress. Please vote and follow along :) 

HI @MariskaWhat a great use case. Currently Rovo Agents in chat can only perform one action at a time, however we are working on bulk actions right now. However, you can accomplish this using Rovo Agents and Confluence Automations. I've made a loom here to walk you through…

@Dirk De Mal -- Were really close to opening up to more users, so hang tight and you should have access real soon! 

Our immediate focus is optimizing the virtual agent for service teams that capture and resolve requests in Slack. We will begin work on supporting additional channels like Microsoft Teams shortly. Please keep an eye on the community and our public cloud roadmap for an update!

Hey @Danisse! the JSM Virtual Agent is now available for all! This product guide walks you through step by step setup: https://www.atlassian.com/software/jira/service-management/product-guide/tips-and-tricks/virtual-agent#overview

Hi @Wade H -- apologies for missing this question. Were you able to get it working again? 

Hmm, can you try having her navigate to the "settings" tab and see if she is able to log in? If not, can you open a support ticket here: https://support.atlassian.com/contact/#/ It be helpful to share any errors in your console. Thank you and apologies for the issue!