diff --git a/.gitlab/issue_templates/Bug report.md b/.gitlab/issue_templates/Bug report.md
new file mode 100644
index 0000000000000000000000000000000000000000..335adf20675a13556258f1c30d8b094cc29c7205
--- /dev/null
+++ b/.gitlab/issue_templates/Bug report.md	
@@ -0,0 +1,47 @@
+<!-- 
+    See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/
+    Writing a good bug report will ensure we'll be able to help efficiently. 🙂 
+-->
+
+#### Summary:
+<!-- Summarize the issue/suggestion concisely: -->
+
+... (write here)
+
+#### Steps to reproduce:
+<!-- Describe what you did (step-by-step) so we can reproduce: -->
+
+- open Inkscape
+- ...
+
+#### What happened?
+
+...
+
+#### What should have happened?
+
+...
+
+Sample attachments:
+
+<!-- Attach the sample file(s) highlighting the issue, if appropriate. -->
+
+#### Version Info:
+```
+- Inkscape Version: ... <!-- (run inkscape -V or copy from Help → About Inkscape, top right) -->
+- Operating System: ...
+- Operating System version: ...
+```
+
+<!-- 
+    ❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️
+    Please be patient while we try to find the time to look into your issue.
+    Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports.  
+-->
+
+<!-- 
+    Please be careful when/after writing #  for example in logs, code, or versions of linux
+    - use inline code span - single backticks (`) before and after it, like this - `#1618`
+    - use multi-line code block - triple backticks (```) to fence/enclose console logs 
+    - attach long logs as a text file.
+-->
\ No newline at end of file