Differences

This shows you the differences between two versions of the page.

--- processes:issue-tracking [2018/08/24 12:55] – joerg.hampel
+++ processes:issue-tracking [2023/08/18 10:51] (current) – joerg.hampel
@@ Line 1: / Line 1: @@
-====== 02 Issue Tracking ======
+====== 03 Issue Tracking ======
 > //An issue tracking system (also trouble ticket or request management system) manages and maintains lists of issues, as needed by an organization. Issue tracking systems are commonly used by customer support to create, update, and resolve reported customer issues, or even issues reported by that organization's other employees.//
@@ Line 6: / Line 6: @@
 ===== Introduction =====
-As our code repositories are managed on a [[https://about.gitlab.com/|GitLab]] server, we use GitLabs integrated Issue Tracker. Having a united platform for source code version control and issue tracking lets us connect issues to code revisions in a very easy and natural way.
+As our code repositories are managed on a [[kb:scc:gitlab|GitLab]] server, we use GitLab's integrated Issue Tracker. Having a united platform for source code control and issue tracking lets us connect issues to code revisions in a very simple and natural way.
 ===== Issue Tracking with GitLab =====
-If you have a valid GitLab user and we granted you access to the GitLab repository, you can also manage issues directly from the [[https://about.gitlab.com/images/feature_page/issues_full.png|GitLab web interface]].
+If you have a valid user on the [[https://code.hampel-soft.com/|HSE GitLab Server]] and we granted you access to a repository, you can manage issues directly from the [[https://code.hampel-soft.com/|GitLab web interface]].
+==== Labels ====
+You can find a list of labels we usually apply, together with their meaning, at [[https://code.hampel-soft.com/groups/open-source/-/labels]].