You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: cover RSS/Atom status page feeds and incident list enhancements (#48)
Document three user-facing features shipped in the last two weeks:
- RSS/Atom feeds for public status pages (subscriptions.mdx): add a
dedicated section covering the feed URLs, content rules, cache
semantics, and Atlassian Statuspage migration path.
- Incident list team filter and new alert_event_cnt counter with the
active-aggregation merge indicator (search-view-incident.mdx).
- Matching changelog entry dated 2026-04-07 in both locales.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
<Updatelabel="2026-04-07"description="📡 Status Page RSS/Atom Subscriptions and Incident List Enhancements">
8
+
9
+
### RSS/Atom Feeds for Public Status Pages
10
+
11
+
Public status pages now expose event feeds in both RSS 2.0 and Atom 1.0 formats. Visitors can subscribe through any RSS reader or automation tool — no email confirmation required:
12
+
13
+
- Every public page serves four URLs: `feed.rss`, `feed.atom`, `history.rss`, and `history.atom`. The `history.*` pair is an alias for Atlassian Statuspage compatibility
14
+
- Feeds include incidents and maintenance events published in the last 90 days, up to 50 items, ordered by start time descending
15
+
- Hidden sections and components are automatically filtered out and do not appear in the feed
16
+
- Responses support `ETag` / `If-None-Match` and return `304 Not Modified` on cache hits
17
+
18
+
See [Subscription management](/en/on-call/statuspage/subscriptions) for details.
19
+
20
+
### Team Filter on the Incident List
21
+
22
+
The global **Incident Management** incident list adds a **Teams** filter that narrows incidents by the team that owns each channel. The filter is hidden automatically when you drill into a single channel.
23
+
24
+
### New Alert Events Counter on Incident Rows
25
+
26
+
Each incident row now surfaces an **alert events** counter alongside the existing **associated alerts** count. When a new event has been merged in the past 5 minutes, the merge icon turns orange, making it easy to spot incidents that are still actively aggregating. Hovering reveals the associated alert count, associated event count, and the time of the most recent merge.
27
+
28
+
</Update>
29
+
7
30
<Updatelabel="2026-03-25"description="🤖 AI Post-Mortem, AI Assistant, and External Incident Submission">
Copy file name to clipboardExpand all lines: en/on-call/incident/search-view-incident.mdx
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Flashduty On-call provides two entry points to view the incident list. One is wi
18
18
| 3 | Processing Progress | Filter incidents by progress, defaults to **All**|
19
19
| 4 | Time Filter | Supports relative time and custom range filtering |
20
20
| 5 | Search | Supports searching by incident ID; if assignee is set to "Assigned to Me", also supports fuzzy matching on "Incident Title" |
21
-
| 6 | More Filters | Supports rich dimension filtering including severity, labels, or custom fields |
21
+
| 6 | More Filters | Supports rich dimension filtering including severity, channels, teams, labels, or custom fields. The **Teams** filter is only visible under the global Incident Management entry and narrows incidents by the team that owns each channel|
22
22
| 7 | View Settings | Supports rich rendering options including **custom display attributes** and even aggregate views |
23
23
| 8 | Pagination | Pagination and items per page adjustment |
24
24
@@ -59,6 +59,15 @@ Flashduty On-call provides filtering capabilities across various dimensions with
59
59
Flexibility often means lower performance, and Flashduty On-call is no exception, despite our many performance optimizations. We always recommend narrowing your query time range and using conditions like **Assigned to Me** and **Processing Progress** to reduce query scope.
60
60
</Tip>
61
61
62
+
### Row content
63
+
64
+
Beyond the title and progress, each incident row surfaces two key counters:
65
+
66
+
-**Associated alerts**: total number of [alerts](/en/on-call/channel/noise-reduction) grouped into this incident
67
+
-**Alert events**: cumulative count of events merged into the incident. When a new event has been merged in the past **5 minutes**, the merge icon turns orange to signal that the incident is still actively aggregating
68
+
69
+
Hovering over the counters opens a tooltip with the associated alert count, associated event count, and the relative time since the last merge.
70
+
62
71
### Custom Rendering
63
72
64
73
Click the **Settings** button in the upper right corner of the incident list to customize display content and interaction behavior:
Copy file name to clipboardExpand all lines: en/on-call/statuspage/subscriptions.mdx
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@ Different status page types support different subscription methods:
14
14
| Status page type | Subscription method | Description |
15
15
| --- | --- | --- |
16
16
|**Public**| Email | Visitors subscribe with an email address; email confirmation is required |
17
+
|**Public**| RSS/Atom | Subscribe to event updates via any RSS reader or automation tool; no confirmation required |
17
18
|**Internal**| IM integration | Internal users receive push notifications through linked IM platforms |
18
19
19
20
---
@@ -44,6 +45,36 @@ If the visitor changes their subscription scope before confirming, the system up
44
45
45
46
Internal organization users can receive event push notifications through their linked IM integrations (Feishu/Lark, Dingtalk, WeCom, Slack) after accessing the internal status page. IM subscriptions do not require email confirmation.
46
47
48
+
### RSS/Atom subscription (public status pages)
49
+
50
+
Every public status page automatically exposes an event feed in both RSS and Atom formats, so visitors can subscribe to updates through any RSS reader (Feedly, Inoreader, etc.) or automation tool. Feeds are anonymous — no account or email confirmation is required.
51
+
52
+
Each public status page serves the following four URLs. They return identical content; the `history.*` pair exists as an alias so that Atlassian Statuspage subscribers can migrate without changing their feed URLs:
53
+
54
+
| URL pattern | Format |
55
+
| --- | --- |
56
+
|`{page-url}/feed.rss`| RSS 2.0 |
57
+
|`{page-url}/feed.atom`| Atom 1.0 |
58
+
|`{page-url}/history.rss`| RSS 2.0 (alias) |
59
+
|`{page-url}/history.atom`| Atom 1.0 (alias) |
60
+
61
+
`{page-url}` is the public URL of the status page — either the custom domain (for example `https://status.example.com`) or the default Flashduty-assigned URL.
62
+
63
+
Feed contents follow these rules:
64
+
65
+
- Includes events published within the last **90 days** (both incidents and maintenance), up to **50 items**, ordered by start time descending
66
+
- Only visible component impacts appear in the feed: components or sections marked as hidden are filtered out
67
+
- Each item's `<updated>` timestamp reflects the most recent timeline update, so readers can detect new activity on refresh
68
+
- Responses support `ETag` / `If-None-Match` and return `304 Not Modified` when nothing has changed
69
+
70
+
<Note>
71
+
Feeds are available for **public** status pages only. Requesting a feed URL for an internal or non-existent page returns `404 Not Found`. For internal pages, use IM integrations instead.
72
+
</Note>
73
+
74
+
<Tip>
75
+
If you are migrating from Atlassian Statuspage, you can swap the existing `history.rss` / `history.atom` subscription URLs for your Flashduty status page URL — no change is needed on the subscriber side.
0 commit comments