So when using Rovo it is unaware of custom fields and we use them extensively within Jira and JSM.
I found a way in Automation by passing the values through to a prompt.
However this only works when dealing with 1 issue, rather than asking it to review and evaluate a group of issues based on a custom field.
I completely agree - this would be a great addition! As a vendor with a custom field app, we would appreciate support for third-party custom fields (e.g. object types).
Hi Paul, would you mind submitting a feature request?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dr Valeri Colon _Connect Centric_ ,
sure, will do, but I am unsure where to put it... I will think about it and post the link then
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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" options within Atlassian products or submit a support ticket via the Atlassian Support portal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Dr Valeri Colon _Connect Centric_ is right, the direct link to this request is here:
https://jira.atlassian.com/browse/ROVO-137
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Update on custom fields-- they should be working now. Give 'em a try.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Quick update for anyone who finds this post: They have added custom field support for Rovo agents as of June 10th 2025!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 summarized somewhere it can access, like a linked Confluence page or summary table.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.