From 2442e5a39fb147713b6d6fed27935e25d5b10089 Mon Sep 17 00:00:00 2001
From: Lars Simon Winzer <lars.winzer@stud.unibas.ch>
Date: Thu, 19 Mar 2026 15:29:47 +0100
Subject: [PATCH 1/6] Add: Bug report template

---
 .gitlab/issue_templates/bug_report_client.md | 31 ++++++++++++++++++++
 .gitlab/issue_templates/bug_report_server.md | 30 +++++++++++++++++++
 2 files changed, 61 insertions(+)
 create mode 100644 .gitlab/issue_templates/bug_report_client.md
 create mode 100644 .gitlab/issue_templates/bug_report_server.md

diff --git a/.gitlab/issue_templates/bug_report_client.md b/.gitlab/issue_templates/bug_report_client.md
new file mode 100644
index 0000000..d1b4373
--- /dev/null
+++ b/.gitlab/issue_templates/bug_report_client.md
@@ -0,0 +1,31 @@
+## Bug Report
+
+### Summary
+<!-- Short, precise description of the bug -->
+
+### Affected Component
+<!-- e.g. Lobby Menu, Global Chat, Loading screen, ... -->
+
+### Steps to Reproduce
+1. Do this first
+2. Then do that next
+3. Lastly, see the unexprected error message ...
+
+### Expected Behavior
+<!-- What should happen? -->
+
+### Actual Behavior
+<!-- What happens instead? -->
+
+### Stack Trace / Error Message
+```
+<!-- Paste stack trace or log output here -->
+```
+
+### Possible Cause
+<!-- Optional: your own hypothesis about the root cause -->
+
+
+/label ~bug
+
+/label ~client
diff --git a/.gitlab/issue_templates/bug_report_server.md b/.gitlab/issue_templates/bug_report_server.md
new file mode 100644
index 0000000..46d7572
--- /dev/null
+++ b/.gitlab/issue_templates/bug_report_server.md
@@ -0,0 +1,30 @@
+## Bug Report
+
+### Summary
+<!-- Short, precise description of the bug -->
+
+### Affected Component
+<!-- e.g. TransportLayer, CommandRouter, UserRegistry, Response, ... -->
+
+### Steps to Reproduce
+1. Do this first
+2. Then do that next
+3. Lastly, see the unexprected error message ...
+
+### Expected Behavior
+<!-- What should happen? -->
+
+### Actual Behavior
+<!-- What happens instead? -->
+
+### Stack Trace / Error Message
+```
+<!-- Paste stack trace or log output here -->
+```
+
+### Possible Cause
+<!-- Optional: your own hypothesis about the root cause -->
+
+/label ~bug
+
+/label ~server
-- 
2.52.0


From 1106c891aa28360c012572536d0a4239568a679a Mon Sep 17 00:00:00 2001
From: Lars Simon Winzer <lars.winzer@stud.unibas.ch>
Date: Thu, 19 Mar 2026 15:33:43 +0100
Subject: [PATCH 2/6] Add: Feature request template

---
 .../issue_templates/feature_request_client.md | 27 +++++++++++++++++++
 .../issue_templates/feature_request_server.md | 27 +++++++++++++++++++
 2 files changed, 54 insertions(+)
 create mode 100644 .gitlab/issue_templates/feature_request_client.md
 create mode 100644 .gitlab/issue_templates/feature_request_server.md

diff --git a/.gitlab/issue_templates/feature_request_client.md b/.gitlab/issue_templates/feature_request_client.md
new file mode 100644
index 0000000..c654230
--- /dev/null
+++ b/.gitlab/issue_templates/feature_request_client.md
@@ -0,0 +1,27 @@
+## Feature Request
+
+### Summary
+<!-- Brief description of the desired functionality -->
+
+### Motivation / Problem
+<!-- What problem does this feature solve? Why is it needed? -->
+
+### Description
+<!-- Detailed description of the desired behavior -->
+
+### Affected Components
+<!-- Which existing components are affected or need to be extended? -->
+<!-- e.g. Lobby Menu, Global Chat, Loading screen, … -->
+
+### Acceptance Criteria
+<!-- What must be fulfilled for this feature to be considered done? -->
+- [ ] 
+- [ ] 
+- [ ] 
+
+### Open Questions / Trade-offs
+<!-- Are there design decisions that still need to be discussed? -->
+
+/label ~enhancement
+
+/label ~client
diff --git a/.gitlab/issue_templates/feature_request_server.md b/.gitlab/issue_templates/feature_request_server.md
new file mode 100644
index 0000000..38d3377
--- /dev/null
+++ b/.gitlab/issue_templates/feature_request_server.md
@@ -0,0 +1,27 @@
+## Feature Request
+
+### Summary
+<!-- Brief description of the desired functionality -->
+
+### Motivation / Problem
+<!-- What problem does this feature solve? Why is it needed? -->
+
+### Description
+<!-- Detailed description of the desired behavior -->
+
+### Affected Components
+<!-- Which existing components are affected or need to be extended? -->
+<!-- e.g. CommandRouter, SessionManager, UserRegistry, … -->
+
+### Acceptance Criteria
+<!-- What must be fulfilled for this feature to be considered done? -->
+- [ ] 
+- [ ] 
+- [ ] 
+
+### Open Questions / Trade-offs
+<!-- Are there design decisions that still need to be discussed? -->
+
+/label ~enhancement
+
+/label ~server
-- 
2.52.0


From 090d77054c028d79c4413c265d0ed973753ea1af Mon Sep 17 00:00:00 2001
From: Lars Simon Winzer <lars.winzer@stud.unibas.ch>
Date: Thu, 19 Mar 2026 15:46:25 +0100
Subject: [PATCH 3/6] Add: Protocol schema modification template

---
 .gitlab/issue_templates/protocol_change.md | 42 ++++++++++++++++++++++
 1 file changed, 42 insertions(+)
 create mode 100644 .gitlab/issue_templates/protocol_change.md

diff --git a/.gitlab/issue_templates/protocol_change.md b/.gitlab/issue_templates/protocol_change.md
new file mode 100644
index 0000000..9846910
--- /dev/null
+++ b/.gitlab/issue_templates/protocol_change.md
@@ -0,0 +1,42 @@
+## Protocol / API Change
+
+### Summary
+<!-- Brief description of the protocol change -->
+
+### Affected Commands / Responses
+<!-- Which commands or response types are being added, changed, or removed? -->
+
+| Command | Response | Type of Change | Description |
+|---------|----------|----------------|-------------|
+|         |          | New / Changed / Removed | |
+
+### New / Changed Syntax
+```
+<!-- Before / after or new command syntax here -->
+<!-- Example:
+BEFORE: LOGIN UNAME=<username> PASS=<password>
+AFTER:  LOGIN USERNAME=<username> PASSWORD=<password>
+-->
+```
+
+### Affected Implementation Layers
+<!-- Which components / classes need to be updated? -->
+- [ ] `Session`
+- [ ] `User` or `UserRegistry`
+- [ ] `Tokenizer` / `RequestTokenClassifier`
+- [ ] `ProtocolParser`
+- [ ] `CommandParserDispatcher` + corresponding `CommandParser`
+- [ ] `CommandHandler`
+- [ ] `Response` hierarchy
+- [ ] `GameEngine` or `GameState`
+- [ ] Client-side (create your own issue and create link)
+
+### Migration Strategy
+<!-- If breaking change: how will migration be handled? -->
+
+### Motivation
+<!-- Why is this protocol change necessary? -->
+
+/label ~protocol
+
+/label ~server
-- 
2.52.0


From 0ff4e320ba0862b53609259b70a7f3af2b29dacd Mon Sep 17 00:00:00 2001
From: Lars Simon Winzer <lars.winzer@stud.unibas.ch>
Date: Thu, 19 Mar 2026 15:48:11 +0100
Subject: [PATCH 4/6] Add: Task template

---
 .gitlab/issue_templates/task_client.md | 25 +++++++++++++++++++++++++
 .gitlab/issue_templates/task_server.md | 25 +++++++++++++++++++++++++
 2 files changed, 50 insertions(+)
 create mode 100644 .gitlab/issue_templates/task_client.md
 create mode 100644 .gitlab/issue_templates/task_server.md

diff --git a/.gitlab/issue_templates/task_client.md b/.gitlab/issue_templates/task_client.md
new file mode 100644
index 0000000..e5f15a3
--- /dev/null
+++ b/.gitlab/issue_templates/task_client.md
@@ -0,0 +1,25 @@
+## Task
+
+### Summary
+<!-- What needs to be implemented? -->
+
+### Context
+<!-- Which part of the system does it belong to? -->
+
+### Affected Components
+<!-- e.g. Controller, View, Model, Network, ... -->
+
+### Dependencies
+<!-- Are there other issues or branches that must be completed first? -->
+
+### Definition of Done
+- [ ] 
+- [ ] 
+- [ ] 
+
+### Notes
+<!-- Optional: implementation hints, links to prior design discussions, etc. -->
+
+/label ~task
+
+/label ~client
diff --git a/.gitlab/issue_templates/task_server.md b/.gitlab/issue_templates/task_server.md
new file mode 100644
index 0000000..c1a1345
--- /dev/null
+++ b/.gitlab/issue_templates/task_server.md
@@ -0,0 +1,25 @@
+## Task
+
+### Summary
+<!-- What needs to be implemented? -->
+
+### Context
+<!-- Which part of the system does it belong to? -->
+
+### Affected Components
+<!-- e.g. Response hierarchy, CommandRouter, UserRegistry, ... -->
+
+### Dependencies
+<!-- Are there other issues or branches that must be completed first? -->
+
+### Definition of Done
+- [ ] 
+- [ ] 
+- [ ] 
+
+### Notes
+<!-- Optional: implementation hints, links to prior design discussions, etc. -->
+
+/label ~task
+
+/label ~server
-- 
2.52.0


From 4df8befd274fe012dabded50208e636ad44ea069 Mon Sep 17 00:00:00 2001
From: Lars Simon Winzer <lars.winzer@stud.unibas.ch>
Date: Thu, 19 Mar 2026 15:51:02 +0100
Subject: [PATCH 5/6] Style: Cleanup and addition of checklist

---
 .gitlab/issue_templates/protocol_change.md | 3 ---
 .gitlab/issue_templates/task_client.md     | 6 +++---
 .gitlab/issue_templates/task_server.md     | 6 +++---
 3 files changed, 6 insertions(+), 9 deletions(-)

diff --git a/.gitlab/issue_templates/protocol_change.md b/.gitlab/issue_templates/protocol_change.md
index 9846910..ac7ebe9 100644
--- a/.gitlab/issue_templates/protocol_change.md
+++ b/.gitlab/issue_templates/protocol_change.md
@@ -31,9 +31,6 @@ AFTER:  LOGIN USERNAME=<username> PASSWORD=<password>
 - [ ] `GameEngine` or `GameState`
 - [ ] Client-side (create your own issue and create link)
 
-### Migration Strategy
-<!-- If breaking change: how will migration be handled? -->
-
 ### Motivation
 <!-- Why is this protocol change necessary? -->
 
diff --git a/.gitlab/issue_templates/task_client.md b/.gitlab/issue_templates/task_client.md
index e5f15a3..f75a1c4 100644
--- a/.gitlab/issue_templates/task_client.md
+++ b/.gitlab/issue_templates/task_client.md
@@ -9,9 +9,6 @@
 ### Affected Components
 <!-- e.g. Controller, View, Model, Network, ... -->
 
-### Dependencies
-<!-- Are there other issues or branches that must be completed first? -->
-
 ### Definition of Done
 - [ ] 
 - [ ] 
@@ -20,6 +17,9 @@
 ### Notes
 <!-- Optional: implementation hints, links to prior design discussions, etc. -->
 
+### Checklist
+- [ ] Linked to other issues or branches that must be completed first?
+
 /label ~task
 
 /label ~client
diff --git a/.gitlab/issue_templates/task_server.md b/.gitlab/issue_templates/task_server.md
index c1a1345..e6206d1 100644
--- a/.gitlab/issue_templates/task_server.md
+++ b/.gitlab/issue_templates/task_server.md
@@ -9,9 +9,6 @@
 ### Affected Components
 <!-- e.g. Response hierarchy, CommandRouter, UserRegistry, ... -->
 
-### Dependencies
-<!-- Are there other issues or branches that must be completed first? -->
-
 ### Definition of Done
 - [ ] 
 - [ ] 
@@ -20,6 +17,9 @@
 ### Notes
 <!-- Optional: implementation hints, links to prior design discussions, etc. -->
 
+### Checklist
+- [ ] Linked to other issues or branches that must be completed first?
+
 /label ~task
 
 /label ~server
-- 
2.52.0


From 918002c8cb725c4fcedd65851263ea2c5e7d474c Mon Sep 17 00:00:00 2001
From: Lars Simon Winzer <lars.winzer@stud.unibas.ch>
Date: Thu, 19 Mar 2026 15:53:58 +0100
Subject: [PATCH 6/6] Remove: Automatic assignment of 'server' label to
 protocol_change issue

---
 .gitlab/issue_templates/protocol_change.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/.gitlab/issue_templates/protocol_change.md b/.gitlab/issue_templates/protocol_change.md
index ac7ebe9..6c5d5b2 100644
--- a/.gitlab/issue_templates/protocol_change.md
+++ b/.gitlab/issue_templates/protocol_change.md
@@ -35,5 +35,3 @@ AFTER:  LOGIN USERNAME=<username> PASSWORD=<password>
 <!-- Why is this protocol change necessary? -->
 
 /label ~protocol
-
-/label ~server
-- 
2.52.0