From 1b22c7a084e5bb422d288de383904c6feb156edd Mon Sep 17 00:00:00 2001
From: Jakub Sztandera <kubuxu@protonmail.ch>
Date: Sun, 26 Mar 2017 20:59:58 +0200
Subject: [PATCH] Change issue template to use Severity instead of Priority

Priority is very much subjective. Severity allows us to state examples
and decide on it objectivelly.

License: MIT
Signed-off-by: Jakub Sztandera <kubuxu@protonmail.ch>
---
 ISSUE_TEMPLATE.md | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md
index 22cee3e0d..13c456666 100644
--- a/ISSUE_TEMPLATE.md
+++ b/ISSUE_TEMPLATE.md
@@ -1,11 +1,16 @@
-<!-- Output From `ipfs version --all`) -->
+<!-- Output From `ipfs version --all` -->
 #### Version information:
 
 <!-- Bug, Feature, Enhancement, Etc -->
 #### Type:
 
-<!-- from `P0` "Critical" to `P5` "Relatively Unimportant") -->
-#### Priority:
+<!-- One of following:
+    Critical - System crash, application panic.
+    High - The main functionality of the application does not work, API breakage, repo format breakage, etc.
+    Medium - A non-essential functionality does not work, performance issues, etc.
+    Low - An optional functionality does not work.
+    Very Low - Translation or documentation mistake. Something that really does not matter much but should be noticed for a future release. -->
+#### Severity:
 
 #### Description:
 
@@ -20,4 +25,4 @@ This is for you! Please read, and then delete this text before posting it.
 The go-ipfs issues are only for bug reports and directly actionable features.
 Read https://github.com/ipfs/community/blob/master/contributing.md#reporting-issues if your issue doesn't fit either of those categories.
 Read https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue.
--->
\ No newline at end of file
+-->