Jaha + Jira

Each action item Jaha extracts — with its owner and due date — is created as a task in Jira, one to one. Nobody re-types the follow-ups, and nobody’s follow-up hides in a notes doc.

You choose the parts: summary only, action items only, or the lot — per rule, and per one-off send. A one-off send can always narrow what a rule would deliver, never widen it.

Connect Jira as a knowledge source and Jaha answers from its content — live in the meeting, with citations. The connector carries its own sharing class and answer scope, so connecting it never widens who can hear what is inside.

A rule names Jira as a destination, the payload parts, and which meetings apply. Failed deliveries retry; unhealthy connections are flagged before they lose data. And every meeting keeps its “sent to” trail — what went to {name}, when, and by whose rule.

Three steps, once. Here they are as they actually run for Jira: