Jensen Fleming Atlassian Team

Hey @tom_hawkins -- here is the community post about it! https://community.atlassian.com/forums/Atlassian-AI-Rovo-articles/A-simpler-way-to-build-Rovo-Agents-in-Studio/ba-p/3227414#M2154 > For example I'd like to know whether migrating just one multiscenario agent to test in the new subagent model whilst leaving the others…

@Frank Sherwood -- Good catch, and sincere apologies on the docs! We’ve corrected theme as of this morning; there was a misprint. In the new model there’s no such thing as a “default subagent” in the old, hard‑required “default scenario” sense. Instead: * The parent agent owns the core/default behavior (its own…

@cbouchard -- I don't have an official date to share at the moment, but we are fast tracking it and we expect you to have access this quarter. You can follow the feature's progress here: https://jira.atlassian.com/browse/ROVO-275

@Aleksander Wielgat -- are you able to send me more information on your agent? It shouldn't have fundamentally changed it so drastically - especially on needing to add additional skills you didn't need before. Can you open a support ticket and add me to the ticket/tell support to send me the ticket in Slack? 

Hi @Arman Nejad -- we aren't using Gemini 1.5 Pro. We are using Gemini 3 Flash, which came out in December.

Apologies for the delay, I was OOO last week. For any issues/errors that you see, it's imperative that you create a support ticket for us. It is very difficult for us to investigate issues via this blog post. I will look into the automation issue, I haven't see any other reports on this, but support tickets will help us…

@Amish Khatri Great question! They're LLM will be changed, we are considering flipping theirs before the April 14th deadline, but for now, you can duplicate an OOTB agent in the same way you can any other agent. Navigate to it -> `...` and click Duplicate.

FYI Details on the extending testing window here: https://community.atlassian.com/forums/Atlassian-AI-Rovo-articles/Extended-Testing-Window-for-New-Rovo-Agents-Backend-Model-Until/ba-p/3214209#M2071 This will be reflected in the UI shortly. 

@neha -- Interesting. Is the new agent you created on the new model? All new agents are on the new model by default. > You can raise a ticket with support here: https://support.atlassian.com/contact/#/

@Stefan Kirchner -- Just a quick update, to diagnose this issue, we will need to know more details on the tools used. We don't believe it's a model issue, other models have a similar limit, so we need to look at the logs. If you can send me a ticket link you create with support, that would be great. Thank you so much. 

@Neha Asthana @Veranika Artamonava @Terranova_ Diego Nicolas -- We have rolled out a fix for this issue, please let me know if it is now working for you. If not, can you please open a support ticket so we can look at the logs. @Stefan Kirchner @Razvan Nechifor -- Did you open a support ticket for this? Can you link it to…

Quick update on our (Atlassian) side -- we've extended this window to allow you to toggle between models until April 14th to give you more time to test and migrate your agents. I will provide a more detailed update soon but wanted to provide this update quickly.

@František Špaček _MoroSystems_ @u400492 @Induprasad S R -- can you all please open support tickets so we can dive into each one?

@Razvan Nechifor can you open a support ticket so we can take a look? Please link it to me so I can follow up on it.

@Stefan Hanitzsch -- where did you see this error? There shouldn't be any limitation there. 

@hayato yamazaki -- this will impact agents you speak with in Rovo Chat side bar, but not Rovo Chat without an agent. Rovo Chat uses a collection of models and is on a different rollout cycle. @Piotr Smialek @Stefan Kirchner This update has shown: * Search / knowledge Q&A * Better answer rate and relevance on Search /…

@Bruno Legeard _Lynqa_ -- We don't have dataset versioning in this release. Something we are exploring. 

@manuel_grande -- Live conversation review is a different stream we are working on. You can follow it's progress here: https://jira.atlassian.com/browse/ROVO-356

@Ariel Kauan -- it is possible in Atlassian created and Forge installed agents :) You just need to be an org admin to edit it. Find the agent in Browse, click Edit agent, then user and perms. 

@Leif Ericson -- they are public by default (we didn't want to change fundamentally what people were used to) , but we will mostly likely adding something on publish that asks you what you want your permissions settings to be prior to publish. 

Hey all! We will be adding Verified to the top of the list when selecting agents, just pending some search work (aka it's in progress) New order of selection will be as follows: 1. (up to) 3 Favorites 2. (up to) 3 Verified 3. (up to) 3 Top used in your org 4. Rest of agents Curious your feedback on that order/number. 

@Justin Millette -- currently only users. Full transparency, groups added a ton of dev complexity which would have delayed this release, so we prioritized getting this version in your hands quickly. Pending feedback from users, we'll consider prioritizing groups/teams. 

@Josh I'm excited to!!! It's coming really soon. We will be launching multiple types of evals, but the one that takes the most preparation is Question & Answer (Q&A) Pairs. A Q&A Pair = a user question + your expected “gold” answer. I’d recommend starting to pull this together now. You can even use Rovo to help pull/draft…

@Rebekka Heilmann _viadee_ Sorry for the delay! Rovo Agents in JSM Portal is live for everyone. We even made a new "surfaces" tab in agents for you to connect it directly from Studio. Just go to your published agent, click Surfaces, then add to portal :) 

@John Elder -- this update released to Agents back in December, coming to Chat very soon. If you are still seeing issues, can you please open a support ticket with us? 

Hey @Rebekka Heilmann _viadee_ and @Peter M -- I don't think this is related to custom fields work, but does sound like an issue with url being read in the automation. Can you open a support ticket and we can log in and take a look? 

@CL You can add it to the Portal, and soon the HelpCenter to deflect questions. We are exploring pinning agents in Chat as well, but for now the JSM Portal is the best bet for a "service, deflection use case agent" 

@CL -- this skill can be added to any agent, just add the "raise a request" skill in your custom Agent's scenarios. Or if you intend to use it for a full service use case, you an go to your JSM Space settings, click AI Agents, and create a Rovo Agent from there, it will do a smart set up for you. 

We expect the fix for agents to start rolling out this week. We just had a few small nits to work through before we released it broader. We wanted to make sure that there were no issues when everyone got access. 

@Rebekka Heilmann _viadee_ Another Long's Tips and Tricks for ya!