It seems this has some recurring mentions in the community, but some seem to have a different flavor.
In our case, a simple request to ask Rovo to create a list of work items (and Rovo already listed what it would create in the chat), but when promoted to create them, it either:
@Karri Adkins This usually happens when the project’s required-field config doesn’t match what Rovo sees. Even if Assignee isn’t required for humans, Jira may still mark it as required via workflows, field contexts, or issue type schemes—causing silent failures. Check the project’s field configuration, workflow validators, and issue type screen scheme. Run logs in Studio will show the exact field blocking creation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.