Rules and preview

Each connection has a rule that decides which issue events can be sent to its Google Chat space.

Scope

Choose one or more Jira projects, or provide a JQL query. A JQL rule is useful when only a subset of a project should be routed, for example project = OPS AND labels = chat-updates. Check the query with Jira before enabling it. Use project keys and fields available to the app's Jira account context.

Select Preview matching issues to see up to 10 recent issues in the current scope. The preview shows current matches; it does not predict future event volume or guarantee that every future issue will match.

Event types

• Issue created — a Jira issue was created.
• Status changed — the issue moved from one status to another. Optional From and To values narrow the transition.
• Issue assigned — the assignee changed.
• Issue resolved — the issue entered a resolved state.
• Priority changed — the priority changed to High or Highest, subject to the rule's configured threshold.

The app evaluates the rule when Jira sends an event. An event that does not satisfy the saved scope and event conditions is skipped.

Card fields

Administrators can select from the supported fields, including summary, status, assignee, priority, issue type, labels, due date, sprint, and reporter. Sprint is read only when selected. Jira may return no sprint for an issue that is not assigned to one.

Send only the fields the team needs. The destination space is managed by your organization; people who can read that space may see the fields included in cards.

Recommended setup

1. Start with one test project and one Chat space.
2. Add a narrow project or JQL scope.
3. Select only the events and card fields the team needs.
4. Preview matches and inspect the list.
5. Save the rule, send a test message, and confirm the channel receives the intended updates.
6. Expand the scope only after the initial messages look correct.