Configure Settings

Settings

Settings allows users to customize their Blameless experience across the different product areas.

​

Getting Started

Navigate to settings from the main navigation menu. Settings are categorized across the following sections:

• Organization

• Incident Workflows

• Retrospective Preferences

• Bot Settings

• Integrations

• Notifications

• Security

​

Incident workflow configuration

Users can define different workflows per incident type and severities. This allows you to configure settings related to incidents, retrospectives, and integrations for different use cases.

In the Incident Workflow Configuration image above, you will note that there are a series of tabs:

• <Incident Type Name> Default

• <Incident Type Name> S0 label

• <Incident Type Name> S1

• <Incident Type Name> S2

• <Incident Type Name> S3

The left-most tab, <Incident Type Name> Default, identifies the DEFAULT values identified by the Blameless service configuration. All other tabs (Sev0-Sev3), will model their values off the the Default values.

Incident naming schemes

Blameless allows you to customize the naming scheme of incidents. Currently, there are 4 preconfigured naming schemes:

1. Date (YYMMDD)

• Names the incident after the current day that the incident is created on. The 3rd incident created on September 10, 2020 would be named:

   #incident-200910-3
  

  Copy

2. Issue Name (project-issue-id)

• Names the incident after the ticket number, or the project issue ID, in the Jira project/Ticketing system that the incident creates automatically. If an incident is created that creates Jira ticket 93 in the BLME project, the name of the incident would be:

   #BLME-93
  

  Copy

3. Numeric (Incident-123)

• Incremental numbering for incidents. Incidents are named sequentially. The 199th incident created in Blameless would be:

   #incident-199
  

  Copy

4. Petname (Happy-Llama)

• Randomly generated incident name with an adjective or description as the first word and an animal or object as the second word. An example would be:

   #incident-native-gnat
  

​

Retrospective configuration

Custom questions are configured using JSON schema which allows for ultimate flexibility and can be configured per incident type and severity in Settings:

The analysis section can be configured via a markdown template per incident type/severity within Settings:

Settings Access Control​

Settings access control is defined by settings section. There are cases where a user requires access to an org-level setting, such as incident for creating incidents, but should never have access to more senisitve settings, such as integration credentials. Learn more about settings access control.