Linked SLA Alerts
Linked SLA Alerts keeps linked tickets informed about the parent issue’s SLA. Linked tickets don’t need their own SLA—the app uses only the parent issue’s SLA and can post comments and notifications to linked tickets (Jira comment + @mentions, optional Slack or email). The app lives on the parent Jira issue that has the SLA; that issue can have linked issues (standard Jira issue links). Use Send SLA Alert to Linked Tickets on demand, or configure triggers that are evaluated when someone opens or refreshes the Linked SLA Alerts issue panel on the parent (there is no Forge scheduled trigger or background cron; deduping uses Forge Key-Value Store). It is offered on the Atlassian Marketplace as a paid Jira Cloud app; subscription and payment are handled by Atlassian under their terms.
Key Features
- Panel: Send SLA Alert to Linked Tickets — In the issue sidebar (panel title: Linked SLA Alerts), the in-panel heading is “Send SLA Alert to Linked Tickets.” Choose “all linked tickets” or specific issue keys, then click the button. The app posts a comment on each chosen linked ticket with the parent’s SLA status and expiry, and can send the same summary to Slack with clickable Jira links. The message is configurable via the admin “Send SLA Alert to Linked Tickets” template.
- Configurable SLA notifications (panel evaluation) — When someone opens or refreshes the Linked SLA Alerts panel on the parent issue, the app evaluates your configured triggers (at risk, breached, or time-left thresholds you define—multiple rules, units like minutes/hours/days, with separate @mention lists per rule where supported). If conditions match and deduping (Forge KVS) allows, it posts a comment on each linked ticket (not on the parent) about the parent’s SLA and @mentions that linked ticket’s people: assignee, reporter, watchers, and users from configurable custom fields (e.g. Request Participants). Comment text is configurable via the “Custom message template” in admin;
{{issueKey}}there is the parent (the ticket with the SLA). - Admin (Configurations) — Browser title: “Linked SLA Alerts – Configuration.” Configure: optional SLA field override, triggers (at risk / breached / configurable time remaining), who gets @mentioned per trigger (assignee, reporter, watchers, extra users, and “notify from linked-ticket fields”), notification channels (Jira comment, Slack webhook or Bot + channel, automation webhooks on allowlisted hosts), and two templates (panel-evaluated alerts on linked tickets vs Send SLA Alert to Linked Tickets). Slack bot token is stored in Forge Key-Value Store (encrypted at rest); token is masked in API responses and clearable via “Clear saved token” in the UI. The panel includes a “Configure app” link to the admin page.
How It Works
You open the parent issue—the one that has the SLA. The app panel (Linked SLA Alerts) shows “Send SLA Alert to Linked Tickets.” You choose whether to send to all linked tickets or only specific keys, then click the button. The app posts one comment on each selected linked ticket with the parent’s SLA status and expiration; optionally it sends the same summary to Slack with clickable links to those tickets. Separately, when you open or refresh the panel on the parent, the app evaluates configured triggers (at risk, breached, or a time-left threshold—e.g. 30 minutes remaining, among other configurable values and units). If a trigger matches and deduping allows, it posts a comment on each linked ticket and @mentions that ticket’s assignee, reporter, watchers, and any users from configured custom fields. Linked tickets never need their own SLA; they only receive notifications about the parent’s SLA. There is no background scheduler—teams often rely on people opening the parent issue (or use Send SLA Alert when they need an immediate push).
Why It Helps
Support, escalation, and engineering queues often depend on work in other queues. Linked SLA Alerts lets the queue that owns the SLA keep linked tickets informed—whether in the same project or another—without those tickets needing access to the parent project or their own SLA. Best for teams that need to notify downstream work when an SLA is at risk or breached.
Security
The app runs on Atlassian Forge. Configuration and the Slack bot token are stored in Forge Key-Value Store (encrypted at rest per Atlassian). The token is masked in API responses and can be cleared from the UI. Optional Slack and webhook integrations send data to endpoints you configure.
Availability
Install from the Atlassian Marketplace (search for Linked SLA Alerts). Paid subscription and billing are handled by Atlassian under Marketplace terms.
Support & Legal
techcache@proton.me · Support & Security · Legal & Trust · Terms of Service · Privacy Policy
About Tech Cache
Tech Cache builds practical tools and integrations that help teams improve visibility and reduce operational risk within Atlassian environments.