<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Phoenix Incidents</title>
    <description>The latest articles on DEV Community by Phoenix Incidents (@phoenixincidents).</description>
    <link>https://dev.to/phoenixincidents</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F11751%2F6e180fba-b3ce-466c-ae5c-c9e9b55a7081.png</url>
      <title>DEV Community: Phoenix Incidents</title>
      <link>https://dev.to/phoenixincidents</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/phoenixincidents"/>
    <language>en</language>
    <item>
      <title>Phoenix Incidents Now GA</title>
      <dc:creator>Dave Rochwerger</dc:creator>
      <pubDate>Wed, 22 Oct 2025 04:20:24 +0000</pubDate>
      <link>https://dev.to/phoenixincidents/phoenix-incidents-now-ga-15ab</link>
      <guid>https://dev.to/phoenixincidents/phoenix-incidents-now-ga-15ab</guid>
      <description>&lt;p&gt;🚀 We’re live.&lt;br&gt;
&lt;strong&gt;Phoenix Incidents&lt;/strong&gt; is now available on the Atlassian Marketplace.&lt;/p&gt;

&lt;p&gt;We built it for teams that fix things fast but rarely follow through when it’s over—where accountability slips, and lessons get lost.&lt;/p&gt;

&lt;p&gt;We built it because even during an incident, communication breaks down and customer-facing teams are left guessing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Phoenix Incidents&lt;/strong&gt; manages the entire incident lifecycle—start to finish—directly inside Jira and Slack, with built-in guidance to keep everyone aligned:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;💬 Full incident management in Slack or Jira: declare, update, escalate, and resolve from either place. Smart buttons and reminders guide responders through each stage so nothing stalls.&lt;/li&gt;
&lt;li&gt;⚙️ &lt;strong&gt;Best-practice workflows &amp;amp; SLAs by severity:&lt;/strong&gt; pre-defined templates keep teams consistent and on-track, with time-based expectations baked in.&lt;/li&gt;
&lt;li&gt;🔗 &lt;strong&gt;Automatic Jira issue creation and linkage:&lt;/strong&gt; incidents, actions, and follow-ups stay next to your team’s regular work—no context switching.&lt;/li&gt;
&lt;li&gt;🧠 &lt;strong&gt;AI-guided postmortems &amp;amp; RCAs:&lt;/strong&gt; generate structured reports that capture what happened, why, and what to fix—without a blank-page start.&lt;/li&gt;
&lt;li&gt;📊 &lt;strong&gt;Beautiful reporting dashboards in Jira:&lt;/strong&gt; real-time metrics for executives, engineering, and SRE—showing response times, SLA performance, and follow-up completion.&lt;/li&gt;
&lt;li&gt;✅ &lt;strong&gt;Accountability that lasts:&lt;/strong&gt; reminders and dashboards make sure post-incident actions actually get done—within defined SLAs.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It’s the tool we always wanted during those 2 a.m. pages—lightweight, opinionated best practices, no new tools to deal with--just simple.&lt;/p&gt;




&lt;p&gt;👉 Install in Jira on &lt;a href="https://marketplace.atlassian.com/apps/1238126/phoenix-incident-management?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=community_post&amp;amp;utm_content=article_body&amp;amp;utm_vendorID=1053700935" rel="noopener noreferrer"&gt;Atlassian Marketplace&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📖 Or read more at on our website: &lt;a href="https://phoenixincidents.com/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=community_post&amp;amp;utm_content=article_body&amp;amp;utm_vendorID=1053700935" rel="noopener noreferrer"&gt;phoenixincidents.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;We’re excited to finally make this public and can’t wait to see how you run your next incident.&lt;/p&gt;

</description>
      <category>incidentmanagement</category>
      <category>jira</category>
      <category>bestpractices</category>
      <category>slack</category>
    </item>
  </channel>
</rss>
