Unable to setup an automated flow via Power Automate

[Ed Kollar]

I'm unable to connect to our Jira environment or save the connection when trying to setup an automated flow via Power Automate. I use the available connector for Jira Cloud V3 have tried both O Auth and API connectors and have tried on every permission level of Jira account without success. Has anyone successfully setup a Power Automate flow with their Jira space to create a new issue?

[Jason Krewson]

Hey Ed,

I build a lot of Power Automate flows where I work and also support our Jira site, I haven't used the Jira Cloud V3 connector to create work items though. 

I found a great reference that I would recommend reviewing: Jira Power Automate Connector 

In this reference it gives several known issues and limitations, listed below.

• For authentication, you need to use an API token. To get a token, go to this link.
• Basic authentication with passwords is deprecated. For more information, see jira API documentation.
• Jira Server behind a firewall or with REST API disabled is not supported.
• When creating a connection to Jira Cloud, you need to use a valid email address for username. Otherwise, the connection will not be established, although it looks like it's successful.
• Usernames in Jira Cloud are deprecated and cannot be used anymore for fields such as Reporter. For more information, see Atlassian Cloud documentation.
• As per the Jira API documentation, jira API returns maximum 50 projects, so top 50 projects will be listed under dropdown in actions/triggers.
• Pagination was implemented on Get projects. It will return all projects.
• 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.
• The Create a new issue (V3) 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.
• The Project property expected by the connector's actions and triggers should be filled using one of the following options:
  • Pick a project from the project picker. Note that Jira Cloud connections show only top 50 projects in the picker.
  • Use an output from the Get projects action (project's Project Key property).
• For more Edit Issue operation details please see Jira API documentation
• When a working flow starts failing with a 400 response or a bad request for any action or trigger, please check if the API key used to create the connection is expired and if so, re-create connection with a new API key.

If you haven't had a chance yet, I would highly recommend reviewing these. 

---

What error are seeing?

If possible, please share the exact error message here.

Also, if you're able to get the flow to run and an action fails, please share the input and output from that failed action. That will help identify whether the issue is with the Jira connection, authentication, permissions, or the action configuration itself.

Just be sure to remove sensitive information (URLs, emails, tokens, IDs, etc.) before posting it.