nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I am trying to create new epics from a jira filter of epics but getting an error

Bhavana Sesha Sai

I am trying to create new epics from already existing epics as templates, rovo agent is not creating the epics and throwing the below error
No operation with name 'set' found. valid operations are: add,set,remove,edit,copy.

I am using OOTB Create work item skill

Accepted answers

Arkadiusz Wroblewski

Hello @Bhavana Sesha Sai

The error text is also a bit misleading. Atlassian already has a Jira Cloud bug where issue creation can return No operation with name 'set' found... even when the real problem is just an invalid field value in the create payload.

https://jira.atlassian.com/browse/JRACLOUD-83663

If I need to be Honest, Jira itself has enough Stable possibilities to do that, Including Automation.

This KB Article should cover and explain any Question regarding that.

Create work item and a Subtask

All comments

Arkadiusz Wroblewski

Hello @Bhavana Sesha Sai

https://jira.atlassian.com/browse/JRACLOUD-83663

If I need to be Honest, Jira itself has enough Stable possibilities to do that, Including Automation.

This KB Article should cover and explain any Question regarding that.

Create work item and a Subtask

Chris Hampshire

Hello @Bhavana Sesha Sai

I understand you are trying to create a new EPIC based off of an existing EPIC template that you have stored in your project space.

In order to try and support the best I can, can you help me understand

How many EPICs are you hoping to create each time? Is it one or several?
Do the EPICs need to change once they are created and if so, what information do you populate in this new EPIC?

Depending on the answer, ROVO may be able to support but also there may be other low touch options such as JIRA automations we can explore.

Thank you

Dr Valeri Colon (Connect Centric)

@Bhavana Sesha Sai adding to @Arkadiusz Wroblewski’s point—this also shows up quite a bit with Rovo’s Create work item skill today. Even if the error says “set,” it’s usually a field mapping or validation issue (required fields, custom fields, or unsupported fields).

If you’re using an Epic as a template, try simplifying the payload first, then add fields back incrementally to find what’s breaking.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

rovo-atlassian-intelligence