Publish and Unpublish Comments
Retroactively publish internal comments to status pages or hide public comments. Control stakeholder communication during and after an incident.
Published: Thursday, 27 August 2026
You can now retroactively publish internal comments to status pages or hide public comments. This gives you precise control over stakeholder communication during and after an incident.
How It Works
| Feature | Description |
|---|---|
| Setup | Open the incident, go to the history timeline, edit a comment, and toggle Publish Comment on Status Pages. |
| Visibility | Published comments appear on status pages that include the affected service. |
| Permissions | The original comment author, Organization Owners, Organization Administrators, and Team Administrators can change this setting. |
Limitations
- The comment only appears publicly if the incident affects a service linked to that status page.
- Hiding a comment does not retract subscriber emails that were already sent.
- After posting, you must use the All Quiet web app to change visibility. Slack, Microsoft Teams, and Mattermost only let you set visibility when you create the comment.
More updates
-
New
Jira Integration: Precise Field Mapping and Safer Two-Way Sync
The updated All Quiet Jira integration offers precise field mapping, two-way sync without loops, and better priority controls for incidents. These changes improve automation reliability and reduce manual configuration for teams.
-
New
Override Incident Dates and Times
Set custom start and end times for incidents on status pages so stakeholders see the real customer-impact window. All Quiet keeps your internal audit timestamps unchanged.
Published