Recently active topics

Based on the Pagerduty documentation, it seems like “description” field is no longer supported and only the “title” can be retrieved via webhook. These two fields are very different, as one is a quick summary and the other provides scope and context necessary to understand an incident. Is there a workaround to retrieve the description field via webhook? This is normally where we would put a paragraph of additional critical context as such as the Slack thread of a user-reported issue, details about the scope of the issue, etc. Does anyone have any advice on what to do?

Hi team,I’d like to request an enhancement to the List Services API (GET /services) that would make it possible to return custom field values directly within the service objects, without needing additional calls to the Service Custom Fields API.Current ChallengeToday, if you want to retrieve custom field values for all services in your PagerDuty account, you must:Call the List Services API to get the list of services Loop through every service ID Make separate API calls to fetch custom field values per serviceFor accounts with a large number of services, this results in significant numbers of API calls, higher latency, and increased complexity in automation and reporting workflows.Proposed SolutionProvide an optional query parameter (e.g., include[]=custom_fields) to allow the List Services API to return each service along with its custom field values in a single response, similar to how other PD APIs support the include[] pattern for expandable fields.BenefitsReduced API call volume B

The new Slack integration update now @mentions the assigned user directly in the incident message posted to Slack channels. While this is great for high urgency incidents where immediate attention is needed, it's disruptive for low urgency incidents.Our team uses separate Slack channels and PagerDuty services for high vs low urgency alerts. Low urgency alerts have long SLAs and are triaged on a best-effort basis during business hours. Getting repeatedly @mentioned in Slack for these creates unnecessary noise and distractions throughout the day.Is there a way to control this behavior that I'm missing? Ideally something like:A per-service setting to enable/disable user tagging in Slack messages A per-urgency setting (e.g. only tag for high urgency)If not, would love to see this added as a configuration option. Currently there's no way to suppress the @mention without either muting the channel entirely or removing the native Slack integration, both of which lose visibility into the alerts

Hi folks, if a Responder who was previously deemed not needed for an Active Incident is now needed to be re-engaged, how do you accomplish this?

We are excited to announce that the details for PagerDuty on Tour San Francisco are officially locked in!Mark your calendars for a full day of connection, learning, and innovation as we explore the path to autonomous operations.📍 The DetailsDate: May 13, 2026 Venue: The Mint (88 5th St, San Francisco, CA)🎤 Speaker LineupGet ready to hear from industry leaders and PagerDuty executives, including:Jennifer Tejada (CEO, PagerDuty) David Williams (SVP Product Development,  PagerDuty)Rukmini Reddy (SVP Engineering, PagerDuty) Customer Speakers from Intuit, Twilio, Clover, UWM, and Arize AI sharing real-world stories on AI-powered incident management and automation🛠️ Hands-on WorkshopsKick off the day (8:30 AM - 11:00 AM) with interactive sessions designed to level up your skills:AIOps Revolution Bootcamp: Learn to shift from reactive firefighting to proactive prevention. PagerDuty Incident Management Certification: Validate your expertise in best practices and frameworks. Fast Track: Foun