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

Error in Power Automate with Jira Connector

Marcel Wimmer

Hello,

in Power Automate i get an Error with the Jira "Create new issue V2" connector.

Error is:

The dynamic operation request to API 'jira' operation 'ListIssueTypesFields' failed with status code 'BadGateway'. Error response: { "error": { "code": 502, "message": "Field 'reporter' of type 'user' is not supported.

What i unterstood is that i have to set the "Reporter" Field in the Issue Type to "optional", but i am not able to do that in the Project/Issue Type Settings.

Hope someone can help me.

Thanks in advance

Marcel

Accepted answers

All comments

BK Gmail

Not an answer but I am running into the same issue. It had to have worked at some point, or I would have never been able to save the flow. I ended up deleting the Create a new issue (V2) and adding it back.

Fixed for now, but I lost the ability to pass extra fields from SP to Jira, as there is no JSON window available now. Maddening.

Marcel Wimmer_zvon18

Hi Benjamin,

das Problem hat sich bei mir erledigt. Wir hatten noch das "Standard" Helpdesk Template als Projekt im Einsatz. Wir haben uns durch den Jira-Support das ITSM Template freischalten lassen, ein neues ITSM Projekt erstellt und dann hat der Connector auch funktioniert.

LG Marcel

Michael Court_2l8mew

Hi @Marcel Wimmer,

I have had the same issue (I believe it's because the Jira connector cannot handle certain field types) and have been able to work around it by using the HTTP action instead. See here for a guide to get you started.

Jeff Dean

A colleague just told me the answer to this.

If the Jira credentials you are using have access to update the "Reporter" field on the issue, it will throw this error. If you have that update-Report permission removed and just let it default, the connection should work.

chad.leblanc

This! This is the correct answer! I changed my permissions to remove that and it worked like a charm!

Franklin Nirmal Premkumar

Hey Chad,

May I know how you did that?

chad.leblanc

I am part of a Company-Managed Project, but had Project Manager permissions on my board. I made sure there were others that can manage the project outside of me, and once I removed that permission, it worked like a charm!

Im going to be working with my Jira Admin a bit more on setting up a separate permission to change that field, but because I am using my API key in the flow, it's going to default me to the Reporter field and my other admins can change the user after it hits our backlog.

Kyle

Answer - Remove Reporter field as required in the field config scheme.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management