Atlassian Marketplace listing draft

Status: Draft only. The app is not publicly listed, production deployment and Marketplace submission are not part of this task.

App name

Alert Relay for Jira Service Management

Tagline

Route JSM Operations alerts to Google Chat with priority-based delivery and scheduled digests.

Highlights

1. Route Operations alerts to Google Chat

Connect a JSM Operations webhook to an administrator-selected Chat space, test the destination, and map only the alert actions your team wants to receive.

Screenshot caption: Configure the Chat destination and review the JSM Premium or Enterprise requirement before connecting an Operations webhook.

2. Choose immediate and digest policies

Set the minimum priority for immediate delivery and a digest interval for lower-priority events. Review the queue counts for the selected connection before changing its policy.

Screenshot caption: Check separate immediate and digest counts, then set the priority threshold and digest interval for this connection.

3. Review a bounded delivery journal

Inspect recent delivery times, outcomes, HTTP statuses, and fixed error categories per connection. The journal omits alert content, alert IDs, destination URLs, and tokens.

Screenshot caption: Review recent synthetic DEV delivery outcomes without exposing alert payloads or webhook credentials.

The Marketplace image files and exact dimensions are listed in assets/README.md.

Description

Alert Relay for Jira Service Management routes selected Jira Service Management Operations alerts to a Google Chat space chosen by a Jira administrator. Connect the destination, test it, set a priority threshold and digest interval, and review delivery health in Jira.

The direct Operations Webhook integration requires Jira Service Management Premium or Enterprise. An active Atlassian Marketplace license for Alert Relay is also required to configure the app and deliver events. The customer's Google Workspace administrator must allow incoming webhooks in the selected Chat space.

The app processes an allow-list of fields needed for routing and delivery. It does not forward alert descriptions, notes, messages, or attachments. Automation web requests are a separate fallback only where the customer's Jira plan and available Automation triggers support the required payload; they do not provide the full Operations integration on every plan.

Alert Relay is a separate product from Chat Relay for Jira. It handles JSM Operations alerts; it does not subscribe to Jira issue events or send issue-change notifications.

More details

• JSM Operations Webhook events can be mapped to the actions enabled by the site administrator.
• Higher-priority events can be delivered immediately; lower-priority events can be grouped into scheduled digests.
• Events are grouped into Google Chat threads by alert identity.
• The per-connection delivery journal is bounded and intended for diagnosis, not a full event archive.
• Exact request replays are deduplicated within the app's retention windows. Delivery is at least once across ambiguous network failures; exactly-once delivery is not promised.
• HTTP 202 Accepted means an event was accepted or deduplicated by the endpoint. It is not proof that Google Chat displayed a message; check the delivery journal and the destination space.

Requirements

• Jira Service Management Premium or Enterprise for the direct Operations Webhook integration.
• An active Atlassian Marketplace license for Alert Relay.
• Jira administrator access to configure the app and JSM integration.
• A Google Chat space whose administrator permits incoming webhooks.

Listing links

• Documentation: https://darkwoodapps.com/docs/alert-relay
• Support: https://darkwoodapps.com/support/alert-relay
• Privacy: https://darkwoodapps.com/privacy/alert-relay
• DPA: https://darkwoodapps.com/dpa/alert-relay
• Subprocessors: https://darkwoodapps.com/subprocessors/alert-relay

Keywords

Jira Service Management, JSM Operations, incident alerts, Google Chat, alert notifications, on-call, webhook, digest

Owner review notes

• Confirm Marketplace wording, license model, and supported action list after Dev 2 accepts the release candidate.
• Do not claim that the direct native Operations path was tested on a Premium or Enterprise site until that test is completed.
• Keep pricing out of the listing until the Owner approves the per-agent proposal and confirms Marketplace's billable user unit.