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; } } }

create jira issue v3 - not working

Manjunath CM

I am unable to create a Jira Story from one of my Copilot Studio topic flows.

It is not clear whether the problem is with the Jira API design or with Copilot Studio itself.

I am specifically stuck on how to pass the summary and description fields when using the Create a new issue (V3) action.

The documentation and in-product guidance are very limited, which makes it difficult to understand and resolve these errors.

Can someone please help by explaining how to pass the bare minimum required fields, such as summary and description, in the Item payload so that a Jira Story can be created successfully?

Thanks !

Accepted answers

All comments

Tomislav Tobijas

Hey @Manjunath CM ,

If you're looking at the official documentation, the minimum required fields in (general) payload are:

project (by key or id)
issuetype (by name or id, e.g., "Story")
summary
description (this might be optional as well)

Few tips here:

If your Story issue work type or project space has additional required fields (custom fields, components, etc.), you must include those as well, or the API will return an error.
If you get "unknown fields" or similar errors, ensure the fields are present on the Create Work Item screen for that work type and space.

Can you maybe share which errors you're getting when you try to post a payload?

Cheers,
Tobi

Rudy Holtkamp

@Manjunath CM , also be aware that if you use a user token you need to use the as base URL:

<yoursite>.atlassian.net/rest/api/3/issue

But if you use a service account, the URL is different:

https://api.atlassian.com/ex/jira/<CLOUD_ID>/rest/api/3/issue

Manjunath CM

@Tomislav Tobijas

I don’t want to pass any custom fields and just want to try creating a Jira ticket using the bare minimum values with Create a new issue (V3).

My understanding is that project, issue type (ID), and summary are the mandatory fields required for issue creation, and I’d like to know if this is correct.

I’m unable to assign any value to Item since it is a dynamic type.

I’m new to agent creation, so apologies if I’m missing something basic.

Manjunath CM

@Rudy Holtkamp

I have created new connection using Jira API token on Jira Connector.

And using URL in the format..

<yoursite>.atlassian.net/rest/api/3/issue

Tomislav Tobijas

Hmm @Manjunath CM 🤔

I haven't used Microsoft's suite that much, but this "item" field might be the place where you provide the details for the Jira item you want to create.

From what I've managed to find:

This field should be formatted as an object containing the minimum required fields for issue creation:

summary: The title of the issue.

description: (optional, unless required by your Jira configuration)

Any other required fields for your project/issue type (e.g., custom fields, if configured as required in Jira).

So, "item" might need to look like:

{
"summary": "Your summary here",
"description": "Your description here"
}

Again, I haven't built something like that with Power Automated or Copilot Studio to know if this is the right course, but you could try it out.

Potentially, people in the Developer community could know more and help out when it comes to troubleshooting it.

Manjunath CM

@Tomislav Tobijas / @Rudy Holtkamp

any reference to do this with power automate ? request you to share

Because i tried doing this with power automate, but the link is not getting established

Topic Design

in Powerautomate, it expects values in text_1.

Remy Ramirez_i4qhw8

Any update here I have the same issue, I cannot create an issue as the object item is not set and I don't know how to define it to properly share the summary or description.

Praveen Vasudevan_atoj66

So, I asked Copilot to teach me how to do this and this is what was suggested to pass for summary or description. I used variables to store the summary and description. Alternatively, one can replace ${Global.varSummary} with "The actual summary of the issue".

I still haven't managed to get it to work though. I have been stuck with this error for days now:

"The connector 'Jira' returned an HTTP error with code 400. Error code: ConnectorRequestFailure. Conversation ID: 604736ce-07fd-494c-bcee-3f7e79d38216. Time (UTC): 4/14/2026 10:35:58 PM."

Again, Copilot suggested that I provide all the mandatory fields that our company has configured as part of the payload, and I did. The error message is very vague.

Appreciate any help in this regard.

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