Adding Action Items to Incidents

This article describes how to add action items, both during and after an incident.

With FireHydrant, you can track all of your outstanding and completed action items to ensure that all work is accounted for. This is a great way to:

  • keep track of steps to mitigate current issues
  • make your systems more resilient for the future

Note: FireHydrant can sync all incidents and action items with apps that you have integrated, enabling your project managers to track work seamlessly. For example, FireHydrant automatically creates a ticket (in Jira) or story (in Clubhouse) when an incident is declared.

Action Item Types

There are two types of action items on FireHydrant:

  • Tasks. Tasks are action items to be completed during an incident in order to mitigate the issue at hand. While an incident is active, action items will be set to create tasks by default, although that can be overridden.
  • 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. While an incident is resolved, action items will be set to create follow ups by default.

Adding action items from Slack

You can add action items during an incident directly from Slack by running:

/firehydrant add action-item

A dialog box opens, providing fields for a summary, a description, the state of the action item (open, in progress, or done), and the item type (task or follow up). You can also assign the action item to a team member and a Project from here. 

add_action_item.png

Note: Due to limitations in Slack's block rendering, content you enter into the description field in the Action Item dialog box is limited to 2900 characters. To view a description that is longer than 2900 characters, open the action item in the FireHydrant UI or in the UI for any ticketing provider (Jira, etc.) that you have integrated with your FireHydrant instance.

FireHydrant links this new action item to the original ticket or story that was created for the incident. Adding the action item also creates a Jira ticket or Clubhouse story (if you have integrations set up with these apps).

To view all the action items of a given incident, go to the dedicated incident channel and run:

/firehydrant action-items
 

Adding action items from the FireHydrant UI

You can also view and add action items from 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:

mceclip0.png

Retrospective stage:

mceclip1.png

 

 

 

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more