Dr Valeri Colon (Connect Centric) Community Champion

Shout out to @Kythera for piloting the virtual tarot deck and agent with me!

@devpartisan I think this is another good question for your 'principles and practices for agent instructions (ie prompt engineering) in a GitHub repo.' https://github.com/ibuchanan/forge-rovo-metaprompting/tree/main/prompts

@A A Ron Geister _Trundl_ I agree. Currently, Rovo does not have native capabilities to directly access or retrieve detailed Jira configuration elements such as workflows, automation rules, or screen schemes. Consider submitting a features request. To enable Rovo to interact with specific Jira configurations, you would…

I need to bookmark this link https://jira.atlassian.com/secure/Dashboard.jspa you can search to see if the suggestion was already made or go straight to "Suggestion" I think ticket 137 might cover your request. Here's a link to the overall board https://jira.atlassian.com/browse/ROVO You can also use the "give feedback"…

I hear you though—and you're not alone in feeling that way. Consistency is key when integrating tools into your workflow, and when expectations aren’t met, it can definitely add stress. You can view the agent’s instructions by clicking on the three dots (…) next to the agent name, then "View Agent". If you’d like more…

Hi @Jacques I received an email with your other comment. Ideally yes, 100% the person that wrote the question would be the one to accept the answer, unfortunately people rarely do. I'm attempting to mark off questions [see screenshot of my view] we already addressed to (1) improve response time (2) track questions to…

Rovo can reference attachments in Jira issues if they’re indexed and accessible, but it doesn’t currently analyze images or non-text files directly. There’s no upload function for standalone analysis. For now, extracting text from attachments manually or using connected OCR tools is required for Rovo to process the…

Hi Paul, would you mind submitting a feature request?

Rovo agents may not always strictly follow prompt instructions due to underlying model behavior. There's currently no way to fully debug or view the prompt Rovo uses at runtime, and caching can sometimes cause older versions to persist. Try re-deploying the app and renaming the agent to force a refresh. Atlassian has not…

共有いただきありがとうございます。Rovo は Jira の課題分析をサポートできますが、効果的な回答には、より構造化されたデータや要約が必要な場合があります。主要なフィールドをグループ化したり、Confluence にサマリーページを作成して、Rovo に明確なコンテキストを提供すると改善される可能性があります。Premium プランで Rovo が有効になっていれば、追加の設定は不要です。今後のご参考になれば幸いです。

Thanks for raising this. Rovo currently prioritizes results based on translated content, which can affect search accuracy in Korean. Language-specific indexing is still being improved, and feedback like yours helps highlight the need for native-language prioritization. Consider submitting this as a feature request via…

Rovo can connect to SharePoint and surface documentation via natural language search, but it’s designed for internal users, not external customers. Exposing Rovo to customers as a chatbot isn’t currently supported (feel free to submit a feature request). For customer-facing use, you would need a custom front end that uses…

Slack indexing with Rovo typically uses credits based on message volume and access scope. For most users, usage is reasonable unless indexing high-traffic channels. As of now, excluding specific channels isn’t natively supported (feel free to submit a feature request), but you can limit access by controlling which channels…

Rovo can index Slack content for search, but queries must be done via Rovo Search—not directly in Slack. Chatting with Rovo in Slack or creating Jira issues from Slack isn’t supported yet—consider submitting a feature request.

Rovo can suggest Jira issues, but creating epics or stories directly requires proper permissions and supported API access. Ensure Rovo has access via an authorized agent with issue creation rights, and watch for updates as this functionality evolves. Reach out to Atlassian Support directly if the issue persists. 

As of now, Rovo agents cannot access Jira Product Discovery idea insights directly, these insights aren't exposed via the standard REST API. Keep an eye out for feature releases via the https://www.atlassian.com/roadmap/cloud

Rovo’s rollout follows a progressive rollout model, meaning, it doesn’t become available to all customers on the same day. Instead, it's rolled out in waves across different regions and instances to monitor stability and usage. Check in with Atlassian Support for details on your instance.

Great approach, Daniel! Yes, defining a smart value variable for each agent’s output (e.g., {{issueType}}, {{priority}}) and then combining them into one summary comment is the way to go. For inter-agent logic, Rovo doesn’t support direct chaining yet, but you can simulate it by conditioning actions within Automation based…

Rovo can assist with pattern-based categorization, but it doesn’t currently auto-complete tables by example. For now, it works best when given clear instructions in a prompt. You can try asking it to apply the same logic used in the first 10 rows, but results may vary depending on consistency and clarity.

Even with linked Confluence and external docs, Rovo may still flag auditability if the links don’t clearly support traceability or decision-making. The exact criteria aren't fully documented yet, so results can be inconsistent. 

Hi Troy, Atlassian now supports data residency for Rovo in limited availability, including the Australia region. By default, Rovo stores data in the same region as your Jira or Confluence instance—so if those are pinned to Australia, Rovo data will be too. To confirm eligibility and request written assurance, reach out to…

Hi Sofia, this issue could be related to how Rovo interacts with your app or how the resources are indexed. If the template exists but Rovo can’t access it—due to permissions, unsupported formats, or missing metadata—it may appear to get stuck after saying it’s fetching the file.

Yes, AI tools like Rovo can hallucinate when prompts lack context or are ambiguous—this is a known limitation. Atlassian recently added a Deep Research feature to improve accuracy by pulling structured insights from the web, Atlassian apps, and connected tools. You're also right—automatic updates to Atlas goals aren’t…

You're right, Robert—Rovo doesn't currently recognize custom fields by default. Passing values through prompts, like you’ve done with Automation, is a solid workaround for single issues. For multiple issues, though, Rovo can’t yet evaluate across a group using custom fields unless that data is first extracted and…

Hi Dikla! Great to see your interest in Rovo and that you're diving in hands-on. Without data to pull from, AI can fall back on general patterns—which sometimes means confident-sounding answers with unrelated sources (like that random Confluence doc). It’s worth trying again with some content —like a sample Confluence…

There are so many things going on in the community that I'm continually impressed by how you keep up with all of it. 

@__ Jimi Wikman Next time. There were just so many great session to choose from. 

@Rishabh Jhawar thanks for joining in and doing the hard work of teasing through the challenges of product adoption.

I know ya'll are going to have a blast!

Skynet! lol You all are awesome beyond words,