Hi, I am asking Rovo to create a test case in a form of sub-task. In my prompt I am giving instructions on how to populate the fields. While I am getting quite a good draft of test cases, I get answer that sub-task type is not supported by my project, which is not true. Rovo offers a workaround to create a task instead. When I agree, I get Error 400 and the task is not created.
I can edit the draft and proceed to task creation - where i have to populate the mandatory fields. However, the guidance to do this was already in the prompt. It seems to me that there are following issues with Rovo:
- it is currently not able to figure out if the project allows sub-task type
- it is currently not able to execute populating of fields based on instructions in prompt. (the instructions was to copy values from parent to certain fields where I provided the names of the fields)
Can you help?
@Jesko Martin Rovo relies on the project’s exposed issue-type schema, and it can misread sub-task availability when the type is locked behind a workflow or screen config. That’s why it falls back to Tasks and then 400s if a required field isn’t surfaced in the skill. You can fix this by checking the project’s required fields and mapping them in the Jira Create Issue skill. Once the schema is fully exposed, Rovo can create the item reliably.
Welcome to the Community Forums.
Can you add some more information on how you set this Rovo agent up please? Screenshots etc.
Also have you thought about using Rovo with Automation, you can pass information from the output of the agent and use that to create work items and sub tasks etc.
-Ciara
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.