You’re offline. This is a read only version of the page.
Hi,
we would like to create jira issues from power automate. We successfully were able to connect to the jira cloud instance and get information from there.
Now we want to create an issue.
The dropdown has been filded by the connection. But where does the content of the ticket go? I would a least assume to have a field for description and title. Where do I put the ticket information?
Is the connector just broken? What can I do? Thanks
I am able to code, but this does not make sense to me. Please help.
Hi Any update or latest release on that issue? I am having the same error. It is working fine with my configuration in Jira connector but when I try to use my manager's API made connector in my flow then it gives this error. Please update me.
I know this is late, but hopefully it can still help others as I ran into it today and figured out why it happens!
TL;DR - The Reporter field in your project configuration is Required. Update your project configuration(s) to have the reporter field be NOT required.
This is what Power Automate has in the documentation:
The Create a new issue (V2) action supports only simple field types such as 'string', 'number', 'date', and 'datetime' in the dynamic schema. If project configuration has a required fields of complex data types, the operation will fail with the error: "Field '{key}' of type '{type}' is not supported". To workaround this, please change project fields configuration and make these fields not required.
When adding the step in the flow, Power Automate hits up Jira to pull in some of the field information. It immediately finds that the Reporter field is required. PA would want to display that field and accept a Reporter entry, otherwise Jira would reject the new issue.
HOWEVER, the Reporter field is a type called 'user', which is not a string, number, date or datetime, which are the only ones supported by the action. Then, Power Automate doesn't know what to do with the field because it can't handle it, and so results the error.
To bypass this, make the Reporter field in Jira not required for the project(s) you want Power Automate to create tasks in. Do it for Epics, too, if you want to be able to create Epics.
NOTE: This also happens if you try and choose Sub-task for the issue type. Sub-tasks require a Parent Issue, and this field type is called 'issuelink'. Sure enough, 'issuelink' is also not a string, number, date or datetime 🙄. Haven't figured out a workaround for this one out yet, unfortunately..
Thanks for your answer @v-LilyW-msft the other posts also do not have a solution for the issue.
I think that the connector has not been implemented to the end. The question is, who can finish implementing it? Since Atlassian is the vendor, it would be great if they can just fix it. But on the other hand, these are open jira interfaces, maybe this can be solved on MS as well. My company is an MS partner and we think that we could use the power platform for some of our customers, but if it already fails with the basic stuff it is a pity.
Hi @yvette
Thank you for your posting.
Here is a similar post, you can click the link to see if it helps.
Best Regards.
#1
DBO_DV
25
Super User 2025 Season 1
#2
CU09051456-0
22
#3
Michael E. Gernaey
10
Super User 2025 Season 1
Share
Report
All responses (
Answers (