In this onboarding tutorial, we'll go over how to add action items both during and after an incident.

With FireHydrant, you'll be able to track all of your outstanding and completed action items to ensure that all work is accounted for. This is a great way to quickly keep track of both mitigating the issue at hand and making your systems more resilient for the future.

Additionally, FireHydrant can sync all incidents and action items with Jira or Clubhouse, allowing your project management teams to ensure that they're completed. Note that with the integration(s) above, FireHydrant will automatically create a ticket (JIRA) or story (Clubhouse) when an incident is declared.

There are two types of action items on FireHydrant:

  • Tasks
  • Follow ups

Tasks

Tasks are action items to be completed during an incident in order to mitigate the issue at hand.

Follow ups

Follow ups are action items that need to be completed after an incident in order to ensure normal operations and to ensure the issue won't happen again.

Adding action items to an incident

FireHydrant makes it simple to add action items both during and after an incident.

Slack

You'll have the option to add action items during an incident right through slack by typing in:

/firehydrant add action-item

From here, you'll be brought to a dialogue where you'll have the option to include a description, the state of the action item (open, in progress, done), its type (task or follow up), and assign the action item to a team member.

With our Jira and/or Clubhouse integration, this would, in parallel, automatically create a ticket (Jira) or a story (Clubhouse) while also linking to the original ticket or story that was created for the incident.

To view all the action items of a given incident incident, you can type in the following within the dedicated incident response channel:

/firehydrant action-items

FireHydrant UI

You'll also have the option to view and add action items right through the FireHydrant Command Center both during an incident and during the retrospective stage. Action items created during an incident can be both "tasks" and "follow ups". Action-items created during a retrospective are solely "follow ups".

During an incident:

Retrospective stage:

As stated above, with our Jira and/or Clubhouse integration, this would, in parallel, automatically create a ticket (Jira) or a story (Clubhouse) while automatically linking it to the original ticket or story that was created for the incident.

Summary

You'll now be able to create, edit, and track all of your outstanding and completed action items using FireHydrant and/or your favorite tools.

Next, we'll go over how to assign teams, SMEs, and even roles to any given incident.

Did this answer your question?