Rovochat can't populate fields in issues creation mode

[Ricardo Cornejo Avendaño]

I got the custom agent to read a confluence page, analyze it and suggest Epics based on its content. The agent is now able to create a description, a summary, a value proposition, etc. 

When I tell it to create an epic using those fields, executes the command, but only matches the description field, all others are ignored.

any suggestions of how to match all other fields with the details it is proposing?

[Taylor Brown]

It sounds like Rovochat is only mapping the description field but not passing the other values correctly to the issue creation form. This usually happens when the field IDs or names don’t match exactly with what the agent is sending. I’d suggest double-checking the field mapping in your Jira (or whichever platform you’re using) and making sure the agent is referencing the correct keys for summary, value proposition, etc. Sometimes using the API directly helps to test if the fields are being accepted. I faced a similar mapping challenge while experimenting with apps like HappyMod app, where proper alignment of fields and parameters was the key to getting everything to work smoothly