Linked SLA Alerts

Getting Started

1. Install Linked SLA Alerts from the Atlassian Marketplace.
2. Open a parent Jira issue that has an SLA and linked issues (standard issue links).
3. In the issue view, open the Linked SLA Alerts panel—use Send SLA Alert / Send SLA Alert to Linked Tickets on demand as needed.
4. To set up trigger rules (at risk, breached, time-left), channels (Jira, Slack, automation webhooks), and templates, use Configure app in the panel or go to Jira administration → Apps → Linked SLA Alerts (Configurations). Those rules are evaluated on panel load—not on a timer.

How It Works

The app operates on the parent issue (the ticket with the SLA). When someone opens or refreshes the Linked SLA Alerts issue panel on that parent, the app evaluates your configured triggers against the current SLA state. If a trigger matches and deduping (Forge KVS) allows a new notification, the app posts a comment on each linked ticket and @mentions the configured people on that linked ticket. Send SLA Alert to Linked Tickets is a separate, on-demand action in the same panel.

Linked tickets receive notifications about the parent’s SLA. They do not need their own SLA field. For timely automated-style notifications, ensure people who care about the SLA visit the parent issue (or use Send SLA Alert when needed)—the app does not poll Jira in the background.

Configuration

Go to Jira admin settings and select Linked SLA Alerts under Marketplace apps, or click Configure app in the panel.

SLA Field (Optional)

The app auto-detects SLA fields by name. If your site uses a non-standard field name or a different language, enter the custom field ID (for example, customfield_10005) to ensure the app reads the correct SLA.

Jira Service Management (optional)

For Jira Service Management request SLAs (for example “Time to resolution”) that are not exposed as a normal issue field, the app can read request SLA data where the installed scopes allow—see scope read:request.sla:jira-service-management in manifest.yml. Availability depends on your JSM setup and issue type.

Trigger Conditions

Configure which SLA states should result in a notification when the panel evaluates (on open or refresh of the Linked SLA Alerts panel on the parent issue). In addition to At risk and Breached, you can add time-left rules: one or more thresholds (e.g. 30 minutes remaining—example only), with amounts and units such as minutes, hours, or days. Each time-left rule can use its own recipient list (not necessarily the same as At risk or Breached).

• At risk — matches when the parent issue’s SLA is in at-risk status at evaluation time (panel load)
• Breached — matches when the parent issue’s SLA is breached at evaluation time
• Time remaining — matches when the parent’s SLA crosses your configured thresholds at evaluation time (configurable values and units; e.g. 30 minutes remaining)
• Only notify if linked issue is still open — skips notifications for resolved or done linked tickets

Who Gets Notified

Configure @mentions separately per trigger type—including At risk, Breached, and each time-left rule where the product supports it. Notifications are posted as comments on each linked ticket and @mention:

• Assignee
• Reporter
• Watchers
• Additional users (search by name or email)
• Users from custom fields (for example, Request Participants)

Notification Channels

• Jira Comment — posts a comment on each linked ticket
• Jira @Mention — includes @mentions in the comment
• Slack — send via incoming webhook URL or Bot token and channel ID
• Email webhook — send via Zapier, Make, or another integration whose endpoint host is on the app’s Forge external.fetch allowlist (see Privacy Policy and manifest.yml)

Message Templates

Two templates are configurable:

Alerts template — used when a panel evaluation sends a notification (trigger matched + deduping). Available variables:

• {{issueKey}} — the parent issue key
• {{slaName}} — SLA field name
• {{remainingTime}} — time remaining or overdue
• {{status}} — at risk, breached, or a configured time-left state (e.g. 30 minutes remaining)
• {{assignee}} — @mentions as configured

Send SLA Alert to Linked Tickets template — used when you run the on-demand action in the panel (Send SLA Alert / Send SLA Alert to Linked Tickets). Available variables:

• {{issueKey}} — the parent issue key
• {{slaStatus}} — At-Risk, Breached, or In SLA range
• {{expiryDate}} — formatted expiration date
• {{assignee}} — @mentions of the linked ticket’s assignee and reporter

Send SLA Alert / Send SLA Alert to Linked Tickets

From any parent issue with linked tickets, the Linked SLA Alerts panel lets you send an on-demand SLA status update:

• Choose All linked tickets or select Only these and enter specific issue keys.
• Click Send SLA Alert (primary action; labeling may show Send SLA Alert to Linked Tickets for the full flow).
• The app posts a comment on each selected linked ticket with the parent’s SLA status and expiry date.

Security

Linked SLA Alerts runs on Atlassian Forge. Core processing and app configuration use Atlassian infrastructure; Tech Cache does not operate separate long-lived app servers for that core logic.

• Configuration and operational state are stored in Forge Key-Value Store (encrypted at rest per Atlassian).
• When you enable Slack or webhook/automation integrations, payloads are sent only to hostnames on the app’s Forge external.fetch allowlist in manifest.yml (e.g. Slack, Zapier, Make—not arbitrary customer URLs), per your configuration and those providers’ policies.
• Slack bot tokens are masked in API responses and never sent to the browser.
• Tokens can be cleared at any time via Clear saved token in the Configurations page.

Policies, Security & Support

Linked SLA Alerts is offered on the Atlassian Marketplace (including as a paid app). For privacy, infrastructure, security, and support:

• Privacy Policy
• Data Processing Agreement (DPA) — informational; see disclaimer on page
• Terms of Service
• Subprocessors & Infrastructure
• Security Overview
• Product Documentation (this page)
• Support & Security

Index of the above: Legal & Trust.

Slack Setup

Option 1 — Incoming Webhook:

Create a webhook at api.slack.com, then paste the URL into the Slack webhook field in Configurations.

Option 2 — Bot Token and Channel:

• Create a Slack app at api.slack.com.
• Under OAuth and Permissions, copy the Bot User OAuth Token.
• Paste the token into the bot token field in Configurations.
• Enter the channel ID (open the channel in Slack, click the channel name, and select View channel details).

FAQ

Do linked tickets need their own SLA?
No. The app uses only the parent issue’s SLA. Linked tickets just need to exist as standard Jira issue links on the parent.

Does the app work across projects?
Yes. Linked tickets can be in any project on the same Jira site.

What happens if a linked ticket is already resolved?
If “Only notify if linked issue is still open” is enabled in Configurations, the app skips resolved or done tickets.

Where is my Slack token stored?
In Atlassian Forge Key-Value Store, encrypted at rest by Atlassian. It is never sent to the browser or stored outside Atlassian infrastructure.

How do I find my SLA custom field ID?
In Jira, go to Project settings, then Fields, and copy the field ID for your SLA field.

When do configured SLA alerts run? Is there a cron or 24/7 monitor?
No. Linked SLA Alerts does not use a Forge scheduled trigger or background cron. Configurable triggers are evaluated when someone opens or refreshes the Linked SLA Alerts issue panel on the parent issue (the resolver that loads linked SLA data). Deduping uses Forge Key-Value Store. Send SLA Alert to Linked Tickets is separate and runs when you use that action on demand.

Support

Linked SLA Alerts is a paid Atlassian Marketplace app. Tech Cache handles customer support by email only—product questions, bugs, and configuration help.

• Email: techcache@proton.me
• Security: same address—private email only; subject line “Security report — Linked SLA Alerts”. Do not post vulnerabilities to GitHub or a public tracker (see Support & Security)
• Legal & Trust — Privacy Policy, Terms, DPA, Subprocessors & Infrastructure, Security Overview, and Support & Security

About Tech Cache

Tech Cache builds practical tools and integrations that help teams improve visibility and reduce operational risk within Atlassian environments.

← Linked SLA Alerts · ← Back to Tech Cache