Configurable Deduplication Window, On-Call Schedule Improvements, Performance Enhancements

Hey there, firefighters 🧑‍🚒 We've been busy this week! Here's what's shipped for you:

🔔 Configurable Deduplication Window

You can now configure deduplication windows for alerts from 5 minutes to 24 hours, giving you more control over when similar alerts are combined. This flexible setting allows you to adjust parameters to match your team's workflow and reduce alert fatigue.

⌚ On-Call Schedule Improvements

We've given your on-call schedules a significant boost to performance and usability:

• Faster Schedule Loading: Improved on-call shift display performance by filtering shifts to match only the calendar view you're looking at
• Smarter Shift Display: Limited display to 100 most relevant shifts with clear messaging when shifts are being filtered
• Better Date Formatting: Added year information to date displays for improved clarity
• Decluttered View: Removed past shifts with coverage requests to focus on what matters now

📱 Mobile App Updates

• Alert Details Enhancement: Added support for viewing annotations, links, and attachments in the mobile alert details screen
• Developer Experience: Improved development workflow by disabling automatic update checks in development mode

🧰 API & Developer Tools

• API Documentation: We have backfilled tags, summaries, and descriptions for API endpoints to improve your developer experience.
• New Retrospective Endpoint: We added a new /v1/retrospectives endpoint for Retrospective management via the API.

💅 UI/UX Improvements

Incident Timeline Improvements:

• Multi-line Editing: Replaced single-line inputs with spacious text areas for better visibility of your incident notes
• Intuitive Keyboard Shortcuts: Simply press Enter to save your edits (previously required Cmd/Ctrl+Enter)
• Better Named Filters: Updated filters to be more clearly named for easier understanding
• Refreshed Timeline Display: Attachments now trigger an automatic Timeline refresh, ensuring you always see the latest updates

Other Improvements:

• Priority Display Logic: Status reports now automatically hide the priority field if the priority feature is disabled at the organization level
• Beta Features Clearly Marked: Added a Beta tag to the Retrospective collaboration setting so you know what's still in development
• Cleaner Milestones: We've cleaned up the Milestone steps within Incidents with refreshed colors, spacing, and layout

🐛 Bug Fixes

Incident Timeline Bug Fixes:

• Fixed an issue that prevented users from setting Milestone timestamps directly from the Timeline.
• In the elapsed time Milestone view, the "Add milestone" buttons were not opening the modal. This is fixed now.

Runbook Bug Fixes:

• Fixed an issues that showed “NaNm” as the time duration in a Runbook Step when the step was set to repeat but no duration was defined.
• We updated placeholder text for the Microsoft Teams Runbook step from incident-{{ number }} to the correct incident-{{ incident.number }}.
• Fixed a bug in the Liquid template preview that incorrectly handled timestamp formats with timezone parameters.

Signals Bug Fixes:

• The /fh page Slack command now works properly with long target names (we're automatically truncating them to avoid Slack API limits).
• Fixed a bug where the Event Log drawer could break when viewing events without annotations.
• Improved error messages and display when creating Escalation Policies.
• The Calendar timeline view no longer breaks when there are unclaimed shifts.

Status Page Bug Fixes:

• Enhanced the display of Milestone names on status pages.
• Updated some of the wording with scheduled maintenances that incorrectly implied events were happening now instead of in the future.
• Improved histogram to properly list all maintenance events.
• Fixed a bug with timestamps that was causing incorrect timezone names.

Other Bug Fixes:

• Updated tooltip link in measurement definitions.
• Fixed an issue where deleted teams were showing up in the user list. Now it only shows currently active teams.
• Fixed a display issue that occurred when testing custom transposer configurations. We will now display the status parameter in transposition output.