Francisco & Ryan,
Ajit from the Product team here at PagerDuty.
Thanks for your suggestions on how our Postmortems feature could be improved.
Let me address each point in turn:
Assign Severity - Seeing the severity of the incident(s) the postmortem corresponds to.
Have noted this gap for Severity.
For customers using Incident Priority, a separate Timeline entry is created when Priority is set, so this is somewhat visible now.
Assign Team or Service - Assign a postmortem to a team or service.
In the second half of the year, we’ll be investing in making Postmortems respect Teams and Permissions more comprehensively. Check in with us in September to see how that work is lining up and if there’s an opportunity for you to join our Preview (Beta) program.
Filtering Postmortems - With the two above items, the ability to filter postmortems by a team, severity or just any item in the table headers on the postmortem page would be a huge win. This should work the same was as other areas that already use Teams to limit what is seen across the platform.
Noted, this is an area we’re looking to improve while we tackle the Teams/Permissions item cited above.
Attachments - Would be nice to be able to attach files to a postmortem to avoid having people go to different tools to get information related to the incident the pm is for.
What attachment types would you expect Postmortems to support?
At present, inserting URLs into the relevant Postmortem sections could mitigate some of the different tool pain you mention.
Tagging additional Responders and Stakeholders - The ability to assign others to a postmortem instead of just listing the incident commander (owner).
Happy to hear more about this: can you clarify what use case you’re looking to achieve?
Transition Status - Together with tagging, the ability to transition a postmortem through the different status and being able to assign someone for each status.
You can change the ownership of the postmortem as it transitions through the various states (Draft, In Review, Reviewed, etc) so we’re already capable of supporting most of this ask.
Task Assignment - Having the ability to assign tasks with an expected completion date.
This is something we’ve heard, often in the context of exporting postmortem action items to ticketing tools like JIRA. Would exposing an export capability, instead of building a task manager
work for you?
- Support in the API for [at least] retrieving and aggregating Postmortems.
Exposing an API for Postmortems is a longer-term roadmap item, unfortunately not something we’d get to in 2019.
- Pagination on the Postmortems view so that large quantities don’t take 10+ seconds to load.
Noted and something we may be able to tackle in 2019 as part of other Postmortem work.