Many teams use SharePoint lists or forms to capture requests, while Jira is used to track and manage work. Using Power Automate, these SharePoint requests can be automatically converted into Jira issues.
This article explains two supported approaches to achieve this integration with Jira Cloud:
-
Creating Jira issues using Jira REST API (HTTP call)
-
Creating Jira issues by sending emails from Power Automate and processing them using Jira Incoming Mail Handlers
Method 1: Creating Jira Issues using Jira REST API
How it works:
A Power Automate flow is triggered when a SharePoint item is created or updated. The flow then calls Jira’s REST API to create an issue directly in a Jira project.
High-level flow:
SharePoint -> Power Automate -> Jira REST API -> Jira Issue
Configuration steps
Step 1: Prepare Jira authentication
-
Use a Jira Cloud user account (service account recommended)
-
Generate an API token from the Atlassian account
-
Ensure the user has permission to create issues in the target project
Step 2: Create Power Automate flow
Step 3: Configure HTTP action
-
Use the HTTP action in Power Automate
-
Configure it to call Jira’s issue creation REST API
-
Authenticate using the Jira user email and API token
Step 4: Map SharePoint fields
-
Map SharePoint fields (Title, Description, etc.) to Jira issue fields
-
Specify the Jira project key and issue type
Step 5: Test and validate
Method 2: Creating Jira Issues using Email and Incoming Mail Handlers
How it works:
Power Automate sends an email when a SharePoint item is created or updated. Jira retrieves this email from a configured mailbox and processes it using Email Handlers to create issues.
High-level flow:
SharePoint -> Power Automate -> Email -> Jira Incoming Mail Server -> Email Handler -> Jira Issue
Configuration steps
Step 1: Verify Jira Incoming Mail Server
-
Go to Jira Settings -> System -> Incoming Mail
-
Ensure an Incoming Mail Server is configured
-
The mailbox (for example, jira@company.co) must already exist and be accessible
Step 2: Configure Jira Email Handler
Each handler is tied to a specific project and issue type.
Step 3: Understand Catch Email Address
-
The Catch Email Address is not a mailbox
-
Emails must always be sent to the mailbox configured in the Incoming Mail Server
-
The Catch Email Address acts as a filter:
This allows multiple handlers to share a single mailbox and still route issues to different projects.
Step 4: Configure Power Automate email action
-
Use a “Send email” action
-
Send the email to the Jira mailbox
-
Include the Catch Email Address in Cc or Bcc if handler filtering is required
-
Use email subject as Jira summary and body as description
Step 5: Test the flow
For teams that use both SharePoint and Jira, Power Automate helps move requests between them.
Because manually copying requests from SharePoint into Jira is not anyone’s favorite task. 🙂