Rovo Agent seems to not work as expected when I tried to create a Rovo Agent to audit whether a User Story is assigned to a correct SAFe Work Type (Business or Enabler).
Even I provide the custom field ID like "customfield_10067"
@Roger Zhen Wang Rovo can read fields, but it won’t reliably audit custom fields unless the Jira schema is fully exposed through the skill. Even if you provide customfield_10067, the agent may not see it if the field isn’t on the project’s screen or the skill isn’t mapped to it. Check that the field is on the Create/Edit/View screens, then update the Jira “Get issue” skill so the field appears in the JSON Rovo receives. After that, the audit logic works as expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you give some more details about what the Agent is supposed to do exactly and what kind of behaviour you're seeing? There is still some development on custom field support.
I tried a very simple scenario with creating a new Agent to help aduit whether a user specified user story has assgined a solid SAFe Work Type (customfield_10067). But the Agent returns below information even the story I provided has assgined the SAFe Work Type to "Business".
Value: (Empty)
❌ Does NOT meet DoR: The SAFe Work Type field is not set. It should be either "Business" or "Enabler".
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.