Rovo with Data Center

[Olga Meltsin]

Hello,

I would like to clarify a certain matter regarding ROVO  for  DC.:

If I use ROVO's agent to create issues, does the mechanism take into account the constraints enforced by SCRIPT RUNNER, such as required fields defined through BEHAVIOUR, and other similar constraints?

Thanks in advance 

Olga

[Christos Markoulatos]

Hi @Olga Meltsin

As far as i know, Rovo for Data Center works by indexing and interacting with Jira issues through its connector and agents. It respects Jira permissions (users only see what they have access to), but there is no official documentation stating that Rovo enforces ScriptRunner Behaviours or custom field constraints during issue creation. Behaviours in ScriptRunner are applied on the Jira UI layer (issue screens) and rely on server-side validation when users interact with those screens. If Rovo creates issues via the API, these UI-level behaviours typically do not apply, unless you have additional validators or workflow conditions configured.

This is what i believe is the case.

Hope this helps!