Task Work Item is creating by Default by ROVO even we given Other issuetype in the ROVO Instruction

[Aruna Vijayan Sailaja]

We are trying to create a ROVO Agent were it should create Epic and Stories, But ROVO is creating Tasks instead of Epic and Story Issuetype. 

It's taking Default issuetype. Even after given prompt to use Epic issue type it's not considering the instructions.

How to resolve this issue? any alternative or workaround for this issue?

[Dr Valeri Colon _Connect Centric_]

@Aruna Vijayan Sailaja This usually happens when Rovo can’t see or satisfy the requirements for the requested issue type, so it falls back to the project’s default type, often Task. Even if your instructions say to create an Epic or Story, Rovo will only do so if the issue type is enabled for the project, all required fields for that type are on the Create screen (for example, Epic Name for Epics), and the agent collects values for those fields.

To resolve this, confirm the fields are visible and update your agent instructions to ask follow-up questions for any missing mandatory values. As a workaround, some teams create the item as a Task first and then use Jira Automation to move it to an Epic or Story once the required fields are populated.

[Nitisha Paresay]

Hi @Dr Valeri Colon _Connect Centric_ 

Can you please let us know the required fields needed to get the correct issue type created through ROVO

[Dr Valeri Colon _Connect Centric_]

@Nitisha Paresay Rovo can only create an issue type if every field marked as required on that issue type’s Create screen is provided at creation time. For Stories, this usually includes Summary plus any required custom fields your project enforces (such as Priority, Components, or team-specific fields). For Epics, an Epic Name is always required in addition to Summary, along with any other required fields configured for Epics in that project. Because required fields vary by project and issue type, the authoritative list is the project’s Create screen configuration—Rovo must be given values for all of those fields to create the intended issue type successfully.

[Fazila Ashraf]

Hi @Aruna Vijayan Sailaja 

Experienced the exact same what you described today and was so frustrating :( 

Seems to be due to the bug -> https://jira.atlassian.com/browse/ROVO-370

[Nikola Perisic]

Welcome @Aruna Vijayan Sailaja 

In your scenario did you specify to Rovo to emphasize on using Epics and Story issue types instead of Tasks?

[Aruna Vijayan Sailaja]

HI @Nikola Perisic 

I have given prompt like : -

The agent must explicitly set the issue type to "Epic" in the creation payload or form. - Do not rely on the default issue type of the project.

Once agent is asking to check the Work Item before creation the type filed is selected Epic only.

Once I asked to create it, its creating Task

[Nikola Perisic]

@Aruna Vijayan Sailaja 

And does it also behave when you have only Epic issue type? I would suggest to test this on a different project.

[Aruna Vijayan Sailaja]

@Nikola Perisic 

Rovo agent is taking default issue type for project only. I tried to change default issuetype to Test issuetype, it created Test instead of Task.

I want my ROVO agent to ignore default issue type while creating and it should create Epic.

[Nikola Perisic]

@Aruna Vijayan Sailaja 

Instead of focusing on the issue type scheme, just tell it to create Epic issue type.

[Nitisha Paresay]

Hi @Nikola Perisic 

We have given below instructions just to create Epic and Story but still its creating incorrect ones

- The agent must explicitly set the issue type to "Epic" in the creation payload or form.
- Do not rely on the default issue type of the project.

Our agent creates the Epics in 1st Step and then the Stories under the Epic in next steps.