Hello guys!
We’ve been working with ROVO Chat for a while and have noticed its functionality across platforms without requiring a context switch and all, which is cool. However, we’re uncertain about the depth of data it can actually access within our Atlassian environment.
For example, when we attempt to query information specific to Jira teams or details from a single issue (e.g., custom fields, standard fields like the “Team” field), it appears ROVO Chat does not have visibility into this data.
Could you clarify the data scope that ROVO Chat can access across platforms? Is there any official documentation that outlines ROVO Chat’s data accessibility (what it can “touch”, “see”)?
Thank you very much 
2 Likes
@MartinFischer,
We don’t currently have Rovo’s “reach” documented anywhere. It’s a fast changing product and the intent is “everything”. The reality is different based on performance (some fields are more expensive to hydrate) and search quality. But, we would like to close the gap.
Can you give us some of the prompts that reproduce your problem? And can you put the prompts in a bit of context? Like what would it accomplish if you could reach the Team? Why is it valuable/useful?
Hello @ibuchanan
We’re aware of the considerations you mentioned—as well as we are aware that agents could potentially bridge some gaps. However, we’re noticing similar patterns when working with the chat, which might be influenced by the types of prompts we’ve been using
For example, fields like Story Points or Labels often work as expected when we ask to find issues with a specific value of these fields but asking for the actual labels on a given issue frequently fails (not always though). Similarly, while it can locate issues with an Original Estimate set, it struggles to retrieve specific values from that field. Complex queries like listing all labels in a project seem particularly challenging.
You can often see output like “I couldn’t find any specific labels associated with the RS-6 issue. If you need further details, you might want to check directly in the Jira issue …”.
Additionally, it appears that for example the above mentioned Team field is not considered at all. We’ve tried using prompts to evaluate workload by team (e.g., via Story Points, or to just get the organizational information including Jira teams) but found that Jira team data doesn’t seem accessible.
This is something we’ve noticed, as use Rovo in JSM/Jira and we have a lot of custom fields.
When using automation with Rovo I can get round by passing values, but that only works on a single case basis. If I want Rovo to analyse all cases by custom field, it can’t do it.
Custom field support would be extremely useful, even if it meant picking which fields to be indexed
1 Like