User Tools

Site Tools


processes:issue-tracking

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
processes:issue-tracking [2019/10/04 15:20] – joerg.hampelprocesses:issue-tracking [2023/08/18 10:51] (current) – joerg.hampel
Line 6: Line 6:
 ===== Introduction ===== ===== 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 ===== ===== Issue Tracking with GitLab =====
  
-If you have a valid GitLab user and we granted you access to the GitLab repository, you can manage issues directly from the [[https://gitlab.com|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]].
processes/issue-tracking.1570202442.txt.gz · Last modified: 2019/10/04 15:20 by joerg.hampel