Create an AI-powered workflow that connects Microsoft Teams, Loom, and Jira to reduce manual work when creating and updating Jira issues after meetings.

Specifically, the ability for AI to:

Ingest meeting artifacts

• Read and interpret Microsoft Teams meeting notes / recap (and optionally OneNote or other meeting note sources)
• Use Loom recordings and their transcripts/summaries as additional context

Generate Jira-ready content automatically

• Transform the captured meeting notes (and Loom transcript) into:

• • • Jira issue descriptions

• • • Acceptance criteria (e.g., Gherkin-style or bullet-point AC)

• • Optionally propose user stories, tasks, or sub-tasks based on the discussed requirements

Update Jira issues with minimal manual effort

• Either:
  • Auto-populate new Jira issues with the generated description and acceptance criteria, or

• • Propose changes to existing Jira issues for a human to review and apply

• Ideally support some mapping configuration (e.g., which Teams calendar/meetings or Loom videos should be associated with which Jira project or issue types)

Problem this solves
Today, the customer’s team has to manually read through Teams meeting notes and Loom transcripts, then copy, summarize, and rewrite them into structured Jira issue descriptions and acceptance criteria. This is time-consuming, error-prone, and leads to inconsistent quality across issues.

An integrated AI workflow would:

• Dramatically reduce manual transcription and rewriting work

• Improve consistency and clarity in Jira issue descriptions and acceptance criteria

• Help teams move more quickly from meeting discussion to actionable, well-formed Jira work items

Possible solution directions (non-prescriptive)

• A native integration (or set of integrations) where:

• • Loom transcripts and Microsoft Teams meeting notes can be passed to an AI service,

• • The AI generates structured Jira content (description + AC),

• • Jira issues are then created or updated with a human-in-the-loop confirmation step.

• Configuration options might include:

• • Selecting which meetings or Loom recordings should trigger this flow

• • Templates for how descriptions and acceptance criteria should be formatted

• • Permissions/controls to ensure only authorized users or projects are updated.