Jira Email/Form Intake to Issue

Overview

This solution turns inbound work requests into triaged Jira issues and acknowledges the requester automatically. It ships as two flows in one solution, one per intake channel: a Microsoft Forms-triggered flow and a monitored-mailbox flow. Both map the request into a Jira issue (summary, description, issue type, priority, optional component, labels), apply assignment rules, and reply to the requester with the new issue key. A correlation id is minted at the start of each run and stamped onto the Jira description and the acknowledgement email.

Why it matters: requests that arrive by form or email get lost or manually re-keyed. Auto-creating structured Jira issues and acknowledging instantly speeds intake, removes double entry, and gives every requester a reference key.

Both flows ship Off (Stopped).

Use Case

A team takes work requests via a Microsoft Form and a shared/monitored mailbox, and runs delivery in Jira. Operations and developers want every request to land as a triaged Jira issue with the requester acknowledged, without anyone re-typing tickets.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Attachments to Jira

The Jira connector has no attachment operation. Add an HTTP POST to /rest/api/3/issue/{key}/attachments (X-Atlassian-Token: no-check, multipart) with a Key Vault-backed token after Create Issue.

Component routing by keyword

Replace the request-type constant in the email flow with a keyword test on subject/body, and/or set the component dynamically.

Deduplication

Stamp the Forms response id / email internet message id as a Jira label and skip creation if it already exists.

Reply in-thread

Swap SendEmailV2 for Outlook ReplyToV3 using the trigger message id to keep the acknowledgement in the original thread.

Assignee format

Assignment uses Jira Cloud accountId; for Server/Data Center use {assignee:{name}}.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

coalesce(outputs('Parse_Form_Answers')?[variables('varFieldMap')?['summary']], 'New intake request from Microsoft Forms')

coalesce(variables('varAssignRules')?[outputs('Compose_Request_Type')], '')

if(empty(variables('varComponent')), json('[]'), json(concat('[{"name":"', variables('varComponent'), '"}]')))

body('Create_Jira_Issue')?['key']