Action Item Workflows
Action item workflows are triggered on changes to the action item data. Every incident created on the Rootly platform also contains an array of action items. You can leverage the power of workflows to auto create Jira tickets for follow-ups, assign Jira tasks , etc.
Action item workflows are particularly useful for...
- Auto creating/updating Jira tickets for follow-ups post incident resolution
- Auto assigning Jira tickets based on user/team assigned in Rootly
- Notify teams of assigned tasks
Follow the navigation below to begin configuring an action item workflow.
Workflows > Create Workflow > Action Item
There are many trigger events to choose from. Check out what's available to you on this page.
In the example below, the workflow will initiate when a new action item is created for an incident.
Since action items are tied to individual incidents, action item workflows can be configured to check for both action item and incident properties.
There are four action item conditions available.
The type represents the type of action item. It can be either a task or follow up.
In the example above, the type condition will pass if the action item is a task or a follow-up.
The status represents the status of the action item. It can be Open, In Progress, Done, or Cancelled.
Please note, because this is an action item workflow, the status referenced here is the status of the action item, NOT the incident.
In the example above, the status condition will only pass if the action item is done.
The priority represents the priority rating of the action item.
Please don't confuse this priority field with the severity field of an incident. They are NOT the same value.
In the example above, the priority condition will only pass if the action item has a high priority.
The team represents the team that the action item is assigned to.
Even though the available team values to choose from are the same for action items and incidents. Their selected values are independent of each other.
For example, I can have an incident belonging to the Security team and an action item assigned to the Infrastructure team.
In the example above, the team condition will only pass if the action item is NOT assigned to the Test team.
As stated above, action item workflows can be conditioned to check for both action item properties AND incident properties. See the Condition Checks section for details on how incident run conditions are configured and enforced.
Available actions in action item workflows are dependent on the integrated applications. Actions relating to specific applications will become available once those applications are integrated.
In the example below, the workflow will create a Jira subtask in the integrated Jira instance.
If you need help or more information about this integration, please contact [email protected] or start a chat by navigating to Help > Chat with Us.
