From 841017c060cf506ff36a5b88daf3ecc5272f96b5 Mon Sep 17 00:00:00 2001
From: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Date: Mon, 22 Aug 2022 10:51:17 +0200
Subject: [PATCH] docs(issue labeling): explain impact label (#17237)

Co-authored-by: Rhys Arkins <rhys@arkins.net>
---
 docs/development/issue-labeling.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/docs/development/issue-labeling.md b/docs/development/issue-labeling.md
index 6f0c487545..227b907aa6 100644
--- a/docs/development/issue-labeling.md
+++ b/docs/development/issue-labeling.md
@@ -88,6 +88,22 @@ At a high level: critical = needs immediate fix, important = to be prioritized a
 
 Use [this search](https://github.com/renovatebot/renovate/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+-label%3Apriority-1-critical+-label%3Apriority-2-high+-label%3Apriority-3-medium+-label%3Apriority-4-low++-label%3Apriority-5-triage) to find any issues which are missing a priority label.
 
+### Impact
+
+<details>
+    <summary>Impact</summary>
+
+    impact:small
+    impact:medium
+    impact:large
+
+</details>
+
+Use these to assign a impact level to an issue.
+Impact means risk to the end users or their use cases.
+It's used to identify which changes can be made relatively quickly versus those which require great care before merging, due to their chance of negatively impacting a wide number of users if there's a bug.
+It does _not_ mean "amount of work for the maintainers".
+
 ### Platform
 
 <details>
-- 
GitLab