Unable to setup an automated flow via Power Automate

Hi Jason,

Going through your detailed list thank you! Do you know what could cause "Unable to parse Jira configuration. 'projects' are empty" error? Also, haven't seen a connector for Jira "Create Issue" that was anything other than that V3 connector previously mentioned. That is all I'm trying to attempt to do to start. Should be simple right? Right?

The above list was from this documentation Jira Power Automate Connector . 

For your error, I actually found something that's a little old (2024) about that, Unable to create a new issue in Jira from a Microsoft Form submission via Power Automate . 

Sounds like your flow is having issues grabbing a list of projects from your site and from the above refence Atlassian was aware of it, but mentions it's likely an issue with the connector and "the Jira connector is not developed or maintained by Atlassian". 

They recommend:

1. Investigation Suggestion: For resolution or deeper insights, we recommend examining the REST API's response behavior more closely, either by reviewing relevant logs for non-200 status codes or by replicating the API requests using the connector's API token. These steps might uncover the root cause or operational discrepancies leading to the observed issue.

I also think my question in the first comment is still relevant, as it looks like you are running the flow and it's failing. Can you share the input and output of the failing action, this will give us so much more information on what's going on here, why it's failing. To share this just click on the failed run from your flows details page, it will open that run, from there click on the action that failed, in the left hand side you will see "show raw inputs" and "show raw outputs", when you click these it opens a pane on the right, copy past all that into a comment here, be careful to cover up/remove any sensitive information though. Note if you are worried about sharing this information on a public forum, you could always write up what we have discussed here with the error and this input/output, paste it into Copilot, Cursor, or whatever AI you use and it will likely help guide you as well. 

Last, a couple easy things to check:

• Verify your Jira URL is correct, should be https://YourSiteNameHere.atlassian.net
• Make sure the Power Automate connector is using an email, not a username
• Verify your API token is correct (if using API)
• This could be a permission issue, make sure you are an admin of your Jira site or at least have permission to browse projects and create issues for the projects you are wanting to create in (good to check even if you are the admin as not being able to see any projects likely means permissions).
• Also, make sure you check if your project has any required fields, I have seen so many integrations fail due to this and give off errors that don't actually mention a required field was needed. 

Should be simple, maybe, sometimes these things error out and we just have to dig into the output to find the issue, your output of the failed action should tell us what the issue is.

Thanks Jason! Here are the inputs and outputs:

{
"inputs": {
"host": {
"connectionName": "shared_jira_1",
"operationId": "CreateIssue_V3",
"apiId": "/providers/Microsoft.PowerApps/apis/shared_jira"
},
"parameters": {
"X-Request-Jirainstance": "CLASSIFIED",
"projectKey": "Retail Alchemy",
"issueTypeIds": "Story"
},
"authentication": "@parameters('$authentication')"
}
}

The dynamic operation request to API 'jira' operation 'ListIssueTypesFields_V2' failed with status code 'BadGateway'. Error response: { "error": { "code": 502, "message": "Unable to parse Jira configuration. 'projects' are empty.", "source": "msmanaged-na.azure-apim.net", "path": "choose[1]\\when[1]\\choose[1]\\when[6]", "policyId": "", "clientRequestId": "6c722678-0796-49ea-8c04-c172fa9659f0", "dreeSet": "true" } }

This is very helpful. 

I think I see the possible issue right here: "projectKey": "Retail Alchemy". 

Project Key shouldn't be "Retail Alchemy", that seems more like a project name, the key instead would be something like PA, a shortened version of the actual project name. Another example, my project is Jira is name Atlassian and Power Platform, so my key is APP. 

The connector parameter is called projectKey and Microsoft documents that the Jira connector expects a Jira Project Key (or a value returned from the Get Projects action), not the project's display name. Documentation on that is Jira Connector . 

You can see this clearly in your input: 

{
"inputs": {
"host": {
"connectionName": "shared_jira_1",
"operationId": "CreateIssue_V3",
"apiId": "/providers/Microsoft.PowerApps/apis/shared_jira"
},
"parameters": {
"X-Request-Jirainstance": "CLASSIFIED",
"projectKey": "Retail Alchemy",
"issueTypeIds": "Story"
},
"authentication": "@parameters('$authentication')"
}
}

So the possible solution would be having your input give the project key instead of the project name (or a value from Get Projects action instead).

Also, if you still have issues after fixing this so you are providing the project key instead of the name, you could always do a test by adding a Get Projects action using the same Jira connection. If Get Projects cannot return any projects it would confirm the connector is failing to retrieve projects before it ever gets to the Create Issue action, it also would possibly mean permission issue.

Let me know how it goes.