Error when using Rovo Agents to Create Epic

[Anonymous]

Message action error: [Code 400] convoai.rest.bad.request - Failed to invoke action for actionKey: jira-issue-create-bulk

---

As per Solved: Work Item Planner Agent - Wont create things in Ji... I created a copy of the Work Item Planner agent and gave it the necessary knowledge and permissions:

However I keep getting the same error when attempting to have it create an Epic for me:

[Anja Bresemann]

Hi, I am getting the same error when using Rovo to open a Jira ticket. It offers to open the ticket and I click on the button after it drafts the ticket text but then the error appears:  

[Anonymous]

That makes sense Anja! I figured I can't have been the only one but I couldn't find any online reports about this issue at all, so thought I'd raise it! 

[Kyle Burke]

I'm getting the same error when trying to create Epics. I can create them manually but my agent fails every time. 

[Ronald van Sleeuwen]

Same here, I provied all required fields to Rovo but same error keeps popping up.

Tried it with story or task, same error.  Just one simple story with like 5-10 fields.

Rovo shows the summary after providing the details and that summary looks ok.
Clicked Create story but error appears.

Can it that that Rovo is missing permissions to create story in the project? If so, where to set?

[Rebekka Heilmann _viadee_]

Hi @Anonymous and welcome to the Community,

are you trying to create multiple Epics at the same time? 

I assume you clicked on "Create epic" right before that error message?

[Anonymous]

Hello there Rebekka! Thanks for the prompt response! 

I thought of adding that detail into the Q but held off because I thought it was obvious; the one time I forego adding detail haha!

Yes I did click on 'Create epic' before it processed for a minute or two before showing this error 

I assume it was only trying to create the single Epic (as per preceding instructions), but how can I be sure

[Rebekka Heilmann _viadee_]

Sorry - it is obvious but sometimes it's the simple things ;) 

I'll escalate this to the team as it looks like a technical error then, especially with @Anja Bresemann confirming.

[Anonymous]

Thank you Rebekka. Will we hear back from you or the team on this thread?

Additionally, just curious how you go about escalating to Atlassian themselves, as I understand you don't work for them, or do you haha? I'm guessing as a Community Champion you have an escalation path? 

[Anonymous]

Hi @Rebekka Heilmann _viadee_ 

Do you have an ETA on when you'll hear back from the technical team?

I currently see the following, but it's been over 2 days

[Rebekka Heilmann _viadee_]

Hi - unfortunately not. I see the same message as you.

I'll try again via Slack.