The Blameless App for Microsoft Teams allows users to easily orchestrate activities with less toil using a comprehensive framework to work, resolve, and inform regarding issues.
For those who have used Slack before, Microsoft Teams handles the bot commands differently:
- Displaying available commands in Microsoft Teams In Teams, when a user enters the following command in an incident channel, you can retrieve a list of available Blameless commands:
@blameless + type ENTER click the “Send” button (arrow icon) or type ENTER a second time.
- Threads vs. Conversations In Microsoft Teams, Microsoft identifies what Slack calls “Threads” as “Conversations”.
- Where’s the Microsoft Teams response? When you enter an
@blameless
command in Microsoft Teams, scroll down if you do not see the expected result on your screen as the active window does not automatically advance into the viewing frame. - Executing Commands You have to click on the “Run selected command” button after you select a command to execute it.
- Where am I? Look at the structure of the Microsoft Teams Conversation. The Description line at the topic the working frame will identify the location. For example:
Once the Blameless App for Microsoft Teams is installed, you can start an incident in Teams by mentioning the bot@blameless
from any channel that the Blameless Bot has access to.
Upon mentioning the bot, it will provide you a list of command options, including starting an incident and showing recent incidents.
- Click on "Start Incident". The bot will then prompt you to specify a type (required), severity (required), Pagerduty service (if enabled) title (required), description, and a request the relevant Microsoft Teams Team name.
- Start typing the relevant team name and the bot will provide a list of matching names. Once the incident starts, the bot will create a dedicated incident channel and display a summary.
After creating an incident, it's time to work through the incident and manage it with the help of the bot, including tasks, roles, incident lifecycle, data collection and more. The dedicated incident channel will be populated with the incident summary for immediate context.
As a first step, the incident creator will be prompted with some suggested actions to start managing the incident.
In addition to the initial suggestions, the Blameless Bot provides several commands to facilitate workflows during the incident.
The following table lists available bot commands to help manage the various aspects of an incident.
Category | Available Commands |
---|---|
Incident | Assign Incident Role Set Incident Status Set Incident Type Set Incident Severity Set Incident Title Set Incident Description Show Incident Invite User to Incident Mark Incident as Duplicate Resolve Incident Delete Incident |
Tasks | Add Task Assign Task View All Tasks View Your Tasks |
Tags | Show Tags Manage Tags |
On-Call | Show On-Call Show Escalation Policy Trigger Alert |
Timeline Events | Add Timeline Message Show Timeline Events |
Advanced | Assign Retrospective Role Send Retrospective as Email |
Users can assign roles by selecting a role/user combination from the dropdowns.
Upon role assignment, the bot will show a success message and display the tasks list for the current incident phase.
Users can move the incident through the various phases by selecting the incident phase they'd like to transition to.
Users can set the incident type by selecting a new incident type.
Users can change the incident severity by selecting a new severity.
Set Incident Title
Users can set the incident title by entering it in the text area.
Users can set the incident description by entering a description in the text area.
When you are ready to resolve an incident, simply select the option from the dropdown and the bot will resolve the incident and you may begin the retrospective process.
Upon resolution, the bot will provide a final, updated, incident rundown summary in the channel, and an updated task list for the Resolved state.
Upon deleting an incident, the bot will delete the incident channel, as well as the incident itself from the Blameless system.
The Show Incident command will display the latest incident rundown in the incident channel.
You can explicitly invite users to the existing incident by selecting the user from the dropdown. Invited users will automatically be added to the incident team in our web UI as Participants.
- Select the desired action. (i.e., "Invite User to Incident").
- Select the "Run selected command" button.
The "Invite User" search window opens.
- Start your search by entering a name in the "Search for user" dropdown field and click on the "Search" button.
- Click on the "Invite User to Incident" button when you find the desired user.
- Select the next user to invite (if multiple invitations) from the same window and repeat the search process. As each invitation fills, Microsoft Teams will display the invite list below the dropdown field.
Mark Incident as Duplicate
To mark an incident as a duplicate specify the other, duplicate, incident and its ID. As a result, the bot will mark the incident as a duplicate in the Blameless system, adjust the status toDUPLICATED
, and add an entry to the incident timeline to reflect the change.
The Blameless bot facilitates managing tasks during an incident via several commands designed to allow for ease when adding, assigning, and completing your incident tasks.
Tasks provide a mechanism by which you can ensure that certain items are completed or suggested during an incident lifecycle. These tasks can be assigned to each phase of the incident, as well as to a specific role or owner.
As the incident progresses through each subsequent phase, the tasks for that phase will become available.
Tasks are grouped by assigned role or by user, if the role has been assigned to a user, which makes it more obvious if a user already owns a set of tasks. Required tasks are tagged with an asterisk, and if they have links, they are displayed as containing a link.
-
To create a new task, first select a task assignee type:
-
a role specific task or
- a user specific task
- Next, based on your assignee type selection, select either a user or a role to assign the new task to.
- Finally, enter a task description and add the task.
Upon successfully creating a new task, the bot will present the task list which includes the newly created task.
"Task" and "Type of Task" are required fields (*).
-
To assign or reassign a task, first select the Task dropdown command option.
- Select the and complete the following options within the Assign Task window: a. Select a task from the drop down options. b. Select the Task Assignee type. c. Select the Task Assignee (User). d. Select the Task Assignee (Role).
- Finally, click on the "Assign Task" button to assign or reassign the task.
- To mark a task as complete or incomplete, simply select the "View Tasks" command.
- Toggle the task checkboxes accordingly.
- Click "Update".
Upon successfully toggling task states, the bot will respond with a summary of the task changes.
While any user joining the incident channel can create and assign tasks to users, by default, only the user who has been assigned the task (also known as the task owner) can complete or reassign a task to a different user.
Optionally, a designated role that is configurable per incident type can be given the permission to reassign and/or mark any task as completed or uncompleted. Refer to the "INCIDENT ROLE WITH FULL TASK PERMISSIONS" Setting.
The Blameless bot allows you to capture metadata during an incident via our flexible tags mechanism. You can manage and view tags by category helping you to enrich your incident data and reporting.
- To add or remove tags, select the "Manage Tags" option.
You can view your tags at any time via the "View Tags" command.
On-call
The Blameless bot allows you to streamline your on-call workflow during an incident, including the ability to show on-call, escalation policies, and take action by triggering alerts.
You can view the incident timeline at any time, and add a custom event to the timeline via the bot by using our Timeline commands.
- Select the "Add Timeline Message" command.
- Enter the message in the Description field.
- Click on "Add Timeline Message".
During an incident, users can also capture important messages, files, and images as highlights to the incident timeline via the messages action menu. In the top right of the message box click on the ellipse (...) to bring up the “More actions” menu and select “Capture highlight” to automatically capture the text as a new timeline event.
Follow-up actions can be created at any time during an incident. Simply describe the follow-up action in the Teams chat and then mouse over the message.
- In the top right of the message box click on the ellipse (...) to bring up the more actions menu and select "Capture as follow-up action" to automatically create a JIRA ticket from the selected text.
Blameless allows the addition of Tabs into the following Microsoft Teams channels:
- General
- Incident-specific
You can add these tabs from the Blameless Microsoft Teams bot app.
- Open the desired channel (General or Incident-specific).
- Click on the "+" sign located in the upper row of the Channel window. This opens a modal containing a list of supported Apps,
- Click on the Blameless Logo to open the Blameless custom tabs to add to your Channel.
- Select the desired tab.
- Click the "Save" button
- Help
Every Microsoft Team will have a General channel. General is where you can see a log of who has joined and left. Topic-specific information (i.e., Incident channel activities), are found in the associated channel.
Help in the General channel focus on getting the user up and running:
- How to Start an Incident.
- Show a list of unresolved Incidents.
- How to read the Incident's Card contents.
- Link to the Blameless Bot documentation for Microsoft Teams Bot.
Blameless creates specific events associated with an Incident. Topics, conversations, actions, etc. to a specific incident are linked and stored there.
With an Incident channel, you can add two custom tabs:
- Overview
- Help
These custom channels provide more details and support relating to the incident.
When you click on the Overview tab at the top of the Incident, you will see the following subsections:
Within the incident header you can view and adjust crucial incident properties and metadata. The incident header shows the following incident metadata and properties:
- Incident Title
- Incident severity
- Incident status
- Type
- Ticket
- Meeting
Incident Title
Entered at the start of the Incident.
Incident Severity
Supplies the company customized values:
- Sev0
- Sev1
- Sev2
- Sev3
Incident status
Standard status values:
- Investigating
- Identified
- Monitoring
- Resolved
- Duplicated
Type
This is the company-configured Custom Incident Type
Ticket
The link to the auto-generated Jira ticket.
Meeting
The auto-generated link to the Teams Meeting application.
As an incident progresses through its lifecycle, Blameless will automatically capture events and add them to the incident timeline. You can easily see the progression of an incident and key events along the way.
Members of the incident team are shown in the team section. Members that have been assigned to roles will be pinned at the top of the list, followed by the remaining participant members.
When you add the Help tab to an incident, the following information is made available:
- Available Bot Commands
- Incident Overview
- Highlights and Follow ups
- Link to the Blameless Bot documentation
Available Bot Commands
This includes how to open the Command menu as well as a table list of the available commands.
Incident Overview
This contains an explanation of the role of the Overview in the Incident process.
Highlights and Follow ups explanation
This describes the Highlight and Follow up features and how to apply them to an Incident.
Link to the Blameless Bot documentation
A link to the Blameless Bot reference documentation on the Blameless web site.
Users may start a swimlane in an incident channel to track a separate conversation which focuses on investigating a problem based on a theory formulated by the incident commander or other participants in the incident channel. Participants can be invited to join this conversation and can be assigned new tasks in this swimlane to refute or confirm the theory. Once the investigation of this theory is completed, the swimlane can be closed.
Refer to the Microsoft Teams Swimlanes Guide for more information.
From the advanced menu, users can leverage retrospective related commands, for example, including assigning retrospective roles, and the ability to send the retrospective via email.
- Select the desired action. (i.e., "Assign Retrospective Role").
- Select the "Run selected command" button. The "Role select" window opens with two required (*) dropdown fields:
- Assign a user to a retrospective role
- Search for user
- Select the desired Role (i.e., "Owner") from the dropdown.
- Start your search by entering a name in the "Search for user" dropdown field and click on the "Search" button.
- Click on the "Assign Retrospective Role" button when you find the desired user.
- Select the next Retrospective role (if multiple assignments exist) from the same window and repeat the search process. As each role fills, Microsoft Teams will display the assignment below the dropdown fields.
Send Retrospective as an Email
As part of the Available Command options for an Incident, the user can also send the Retrospective, when complete, as an Email to a list of users.
- Display the "Available Commands for Incident".
- Select the "Advanced" dropdown option.
- Locate the "Send Retrospective as Email" command.
- Click on the "Run selected command" button. The "Send Retrospective as Email" window opens.
- Enter the desired user email addresses, separated by spaces.
Note:
- One address minimum is required
- No maximum limits (from the bot perspective) on the number of email addresses included
- Retrospective can be emailed to anyone--there is no requirement to be associated with the incident in question
- Click on the "Send Retrospective as Email" button. Once sent, you will receive confirmation that the Retrospective has been sent.
Note:
- There will be no errors displayed if the email sending fails
- We will receive error only if emails were not properly set for further sending
The Blameless bot supports a variety of integrations that provide streamlined workflows during an incident, including JIRA for ticketing, Microsoft Teams Video, Zoom, Google Meet and GoToMeeting for video bridge, and Pagerduty for on-call management.
With our Blameless bot JIRA integration, a corresponding ticket will be created for each incident, and you may also create follow-up actions as needed during the lifecycle of an incident.
Follow-up actions can be created at any time during an incident.
Simply describe the follow-up action in the Teams chat and then mouse over the message. In the top right of the message box click on the ellipse (...) to bring up the more actions menu and select "Capture as follow-up action" to automatically create a JIRA ticket from the selected text.
With our Blameless bot Microsoft Teams video integration, a Microsoft Teams video bridge will be displayed in your incident rundown so you can collaborate more effectively over video together.
With our Blameless bot Zoom integration, a Zoom video bridge will be displayed in your incident rundown so you can collaborate more effectively over video together.
With our Blameless bot GoToMeeting integration, a GoToMeeting video bridge will be displayed in your incident rundown so you can collaborate more effectively over video together.
With our Blameless bot Google Meet integration, a Google Meet video bridge will be displayed in your incident rundown so you can collaborate more effectively over video together.
With our Blameless bot PagerDuty integration, you can streamline your on-call workflow during an incident, including the ability to show on-call, escalation policies, and take action by triggering alerts.
Comments
0 comments
Article is closed for comments.