Changelog

  • v1.6.0 - July 19, 2020

    Pro plan! Private channels! Invite lists!

    We are now introducing the Pro plan. The first major features are "Private channels" and "Invite lists."

    Private channels
    Sometimes Incidents can contain sensitive information and it's best to keep remediations private while you investigate.

    Invite lists
    Are you always inviting the same 10 people to your new Incident channels? No longer! Run /incident settings to provide a list of users to always invite when you launch a new Incident.

    The Pro plan is $39/month. All existing features today remain on the Basic plan. The Pro plan is great for teams of up to 200. For larger teams, please contact us to learn more about our Enterprise offerings.

  • v1.5.0 - July 5, 2020

    Shortcuts! Bot users!

    Bot users! Finally. Now when you install, a new "Incident" bot user will be added to your workspace. Previously, whenever creating a new Incident channel, it'd automatically invite the user who installed the app. No more!

    Additionally, you can now create Incident channels via Slack's "shortcut" menu.

    Note: Update required. Clicking here will prompt you to re-install Incident. You will retain your existing Incident data.

  • v1.4.0 - July 20, 2019

    Templates! And support for /incident settings.

    Configure your workspace's install of Incident! We're starting off with "Templates." Incidents can be stressful, and Templates allow you to provide a custom start message to the channel.

    Include links to playbooks and dashboards, @mention default users, and even add a good luck message!

    To get started, run /incident settings.

  • v1.3.0 - June 18, 2019

    Adds support for /incident list.

    Wondering what's going on? Want to review a completed incident? Run /incident list to see!

  • v1.2.0 - May 13, 2019

    Adds support for custom slugs in channel names.

    When creating a new Incident, you can now customize the name of the channel! By specifying a slug, your newly created channel will be #incident-{slug}. The default is the current Unix timestamp.

  • v1.1.0 - May 7, 2019

    Adds support for /incident end.

    Now when you've finished your incident response, you can share a final summary and optionally archive the channel. The summary also includes the total duration of the response.

  • v1.0.0 - March 12, 2019

    Initial release.