Issues & Features

GitLab's Issues board will be used for tracking bugs and issues from a coding stand point. This splits Issues into various categories, and allows assigning or claiming these tasks by all the team on Gitlab. It also allows direct creation of new branchs from these issues. It also allows discussion about bugs or issues to be kept connected to the code task it relates to hopefully making it easier to track changes and decisions in the long run.


The idea of issues on Gitlab is of any actionable problem, a bug, a change thats needed, errors or confusion in the code. These issues can be assigned to specific people to deal with or taken on by programmers looking for their next task after having completed and merged a previous task.

When you wish to add or create a new issue go to the gitlab Team19 project page, and click on the issues tab. At the top left of the section their is a New Issue button, click this to start creating a new issue.

Templates have been setup to make it easier to format and submit these in a uniforma nd sensible way. This is available from the drop down menu when creating a new issue.

This fills out the description section with some default values, as well as some information that is requried to be added. Plus some hints and tips of extra stuff to add. The more the better, though discussion and questions about the issue can be added in comments underneath.

The last section at the bottom of the issue allows some extract tags to be attached to the issue.

  • Assignee: This tells who it is assigned to that they should be doing this task and will add it to their todo list.
  • Milestones: Used to connect a selection of issues together. This allows people looking at tasks to judge whats more important.
  • Due date: When it is required to be done by this should be updated to reflect a realistic timeline as problems or other issues arise.
  • Weight: mainly used for bug urgency.
    • Weight of 9 implies it's a game breaking bug and needs to be fixed urgently.
    • No weighting implies it's a minor issue that should be addressed but can wait.