# Post-Incident Review Tags Use tags to categorize Post-Incident Reviews and identify related incidents | Jeli Part of PagerDuty Post-Incident Review tags add contextual data to assist in identifying related Jeli Post-Incident Reviews. When viewing a [Post-Incident Review report](/incident-management/after-incident/jeli-post-incident-reviews/post-incident-review-report), the **Overview** tab will list the applied **Post-Incident Review Tags** and suggest [Related Post-Incident Reviews](/incident-management/after-incident/jeli-post-incident-reviews/post-incident-review-report/related-post-incident-reviews) based on the tags those incidents have in common. You can review these Post-Incident Reviews and find common themes in order to help you find process gaps, prioritize work and highlight organizational systems that work or need investment. For example: 1. **Not all incidents impacting your frontend service are the same, but looking across them you may notice that each Post-Incident Review involving frontend mentions**: a. Team members have difficulty understanding a specific alert. b. Your support team is struggling to find the right engineering team to page. c. An indication of technologies that could use more expertise-sharing (i.e., knowledge silos that might exist in your organization). 2. **You can compare incidents and see where they differ**: a. Process changes made in reaction to previous incidents made subsequent responses more difficult. b. Two incidents with the same impact to customers and underlying services had vastly different triggers, contributing factors and takeaways. You shouldn’t consider them as repeat incidents at all. ![View tags on the Opportunity Report](/images/kb/fe68f7f7600e49eff8da60bc6cd6c45bdb6ee65e7224da8a0c26e1b19b57870f-Screenshot_2025-09-12_at_14.59.30.png) *View tags on the Post-Incident Review Report* > **Availability:** Post-Incident Review Tags are available with the Professional, Business, and Enterprise for Incident Management pricing plans. > > Please [contact our Sales Team](mailto:sales@pagerduty.com) if you would like to upgrade to a plan featuring Post-Incident Review Tags. ## Post-Incident Review Tag Types Post-Incident Review tag types are the broader categories to help organize your Post-Incident Review tags. Some examples include: - Service (default) - Technology (default) - Teams - Vendors - Severity - Impact Jeli starts with two Post-Incident Review tag types: - **Service**: Internal resources created within your company (e.g., things created and managed by your teams). They’re likely acronyms, named after the product they support, or have fun names. - **Examples**: `JSA`, `site-backend`, `Gandalf` - **Technology**: External resources shared between companies (e.g., code languages, data center or cloud provider regions and technology you’re using from vendors). - **Examples**: `python`, `us-east-1`, `consul` > **Tag Names:** Your organization may use **Service** and **Technology** to mean something else, or it may be inclined to interpret those words differently. You can define these two categories in whatever way will be the easiest for those within your organization to understand and adopt. ### Create a New Post-Incident Review Tag Type To create a new Post-Incident Review tag type: 1. Navigate to **Settings** → **Post-Incident Reviews** → **Tag Type**. 2. Click **Create tag type**. 3. Enter a **name** for the tag type. 4. Select **Auto-tag values?** if you want Jeli to [automatically add tag values](#auto-tagging) for this tag type. 5. Click **Create** to save your new tag type. ## Manage Post-Incident Review Tags > **Required User Permissions:** Anyone in your organization can create new tags, add or remove existing tags and delete tags. Post-Incident Review tags are the subcategories that apply at the Post-Incident Review level. An Post-Incident Review tag belongs to only one tag type. For example, within the **Technology** tag type you may have values similar to the following: - AWS - Slack - PagerDuty - Lodash ### Create a Tag > **Post-Incident Review Tag Parameters:** Post-Incident Review tags have the following restrictions: > > - Must be between 3–255 characters long > - Can contain only alphanumeric characters, periods `.`, dashes `-`, underscores `_`, slashes `/` and spaces ` ` > - Not case sensitive 1. Navigate to the **Post-Incident Review** where the new tag will apply. 2. In the **Post-Incident Review Tags** section, click (if the Post-Incident Review already has a tag) or **Add tag(s)** (if the Post-Incident Review does not have a tag). 3. Select the desired **tag type** for the new tag. 4. Click and enter the new tag’s name. If the tag does not exist, you’ll see **Create [tag name]** appear in the dropdown. 5. Click **Create [tag name]** to apply the new tag to the Post-Incident Review. If you’ve enabled [auto-tagging](#auto-tagging) for the tag type you selected, Jeli searches your existing Post-Incident Reviews for mentions of the new tag and applies it. ![Jeli can automatically apply new tags to existing opportunities](/images/kb/b863041e091beb191e6db6828d8e53675bd779e04bbd0d92b52ffb229189b9e2-Screen_Recording_2025-09-12_at_16.21.53.gif) *Jeli can automatically apply new tags to existing Post-Incident Reviews* ### Add an Existing Tag to a Post-Incident Review 1. Navigate to the desired **Post-Incident Review**. 2. In the **Post-Incident Review Tags** section, click (if the Post-Incident Review already has a tag) or **Add tag(s)** (if the Post-Incident Review does not have a tag). 3. Select the desired **tag type**. 4. Select the **tag** from the dropdown list. You can also search by clicking . Adding a tag will update the **Related Post-Incident Reviews** list with other Post-Incident Reviews also using that tag. ### Remove a Tag from a Post-Incident Review 1. Navigate to the desired **Post-Incident Review**. 2. In the Post-Incident Review Tags section, click on the tag you want to remove. The **Related Post-Incident Reviews** list automatically updates. ### Delete a Tag 1. Navigate to an **Post-Incident Review**. 2. In the **Post-Incident Review Tags** section, click (if the Post-Incident Review has a tag) or **Add tag(s)** (if the Post-Incident Review does not have a tag). 3. Select the desired **tag type**. 4. Select the **tag** from the dropdown list. You can also search by clicking . - **Note**: ❗️If the tag you wish to delete applies to the Post-Incident Review you are viewing, it will not appear in the selectable tag list. You must [remove it](#remove-a-tag-from-a-post-incident-review) first and then delete it. 5. Hover over the **tag name** and click the icon. This will open a confirmation modal. 6. Enter the tag as prompted and click **Remove**. This automatically deletes the tag from all Post-Incident Reviews. ![Confirm tag deletion](/images/kb/d7e4ee7e3726dac46edc3a1fb39a223f9716d14dc3cdae23eda7e295f3b4f6de-Group_1_2.png) > **Updating Related Post-Incident Reviews:** When you add, remove, or delete a tag, the **Related Post-Incident Reviews** section will automatically update. You will briefly see a next to this section once this process has completed. ## Auto-Tagging Auto-tagging is an optional setting available for [tag types](#post-incident-review-tag-types). When you create a tag, Jeli automatically searches your Post-Incident Review's Slack messages and matches the tag to message contents. Jeli denotes auto-tags with sparkles (i.e., ✨). If you disable auto-tagging for an Post-Incident Review tag type, you can [manually](#add-an-existing-tag-to-a-post-incident-review) tag Post-Incident Reviews with that tag type. To enable or disable auto-tagging for a tag type: 1. Navigate to **Settings** → **Post-Incident Reviews** → **Tag Type**. 2. Locate your desired tag type and click the **Auto-tag values?** toggle to enable or disable auto-tag for that tag type. - When you disable auto-tagging, you’ll see a confirmation prompt informing you that all future Post-Incident Reviews ingested after disabling will cease auto-tagging with tags of the chosen tag type. > **Case Sensitivity and Special Characters:** The auto-tag search used to match tags with messages is not case sensitive. It returns approximate results when it comes to periods, dashes and underscores, but not for spaces between words. > > For example, a tag of **Node.js** will auto-tag an Post-Incident Review in the instance someone typed `Node-js` but not when they type `Node js`. A tag of **Elasticsearch** will not auto-tag an Post-Incident Review mentioning `Elastic search`, and vice versa. ## Recommendations We recommend defining your tags based on what is frequently used in your organization. After that, you should check a few incidents you’d expect to be automatically tagged with that service or technology. If the expected Post-Incident Review tag did not apply, check the phrasing of the service in the Slack messages across those incidents. We also recommend avoiding common words used frequently in response conversations (e.g., `time` or `update`). ## FAQ **Can I edit the name of an existing Post-Incident Review tag type or tag value?** No. Once a tag type or tag value has been created, the name cannot be changed. **Can I delete Post-Incident Review tag types?** No. At this time it is not possible to delete existing Post-Incident Review tag types. **If I enable auto-tagging on a tag type, will it auto-tag existing tags?** No. Auto-tagging only occurs when you create new tags. Existing tags will not apply to Post-Incident Reviews when you’ve enabled this setting.