GitLab Documentation

GitLab Issues Functionalities

Please read through the GitLab Issue Documentation for an overview on GitLab Issues.

Issues Functionalities

The image below illustrates how an issue looks like:

Issue view

You can find all the information on that issue on one screen.

Issue screen

An issue starts with its status (open or closed), followed by its author, and includes many other functionalities, numbered on the image above to explain what they mean, one by one.

Many of the elements of the issue screen refresh automatically, such as the title and description, when they are changed by another user. Comments and system notes also appear automatically in response to various actions and content updates.

1. New Issue, close issue, edit

2. Todos

3. Assignee

Whenever someone starts to work on an issue, it can be assigned to that person. The assignee can be changed as much as needed. The idea is that the assignee is responsible for that issue until it's reassigned to someone else to take it from there.

Tip: if a user is not member of that project, it can only be assigned to them if they created the issue themselves.

3.1. Multiple Assignees (EES/EEP)

Often multiple people likely work on the same issue together, which can especially be difficult to track in large teams where there is shared ownership of an issue.

In GitLab Enterprise Edition, you can also select multiple assignees to an issue.

Learn more on the Multiple Assignees documentation.

4. Milestone

5. Time Tracking

Note: Both estimate and spend times are set via GitLab Quick Actions.

Learn more on the Time Tracking documentation.

6. Due date

When you work on a tight schedule, and it's important to have a way to setup a deadline for implementations and for solving problems. This can be facilitated by the due date). Due dates can be changed as many times as needed.

7. Labels

Categorize issues by giving them labels. They help to organize team's workflows, once they enable you to work with the GitLab Issue Board.

Group Labels, which allow you to use the same labels per group of projects, can be also given to issues. They work exactly the same, but they are immediately available to all projects in the group.

Tip: if the label doesn't exist yet, when you click Edit, it opens a dropdown menu from which you can select Create new label.

8. Weight (EES/EEP)

Issue Weights are only available in GitLab Enterprise Edition.

Learn more on the Issue Weight documentation.

9. Participants

10. Notifications

Read more on the notifications documentation.

11. Reference

12. Title and description

13. @mentions

To change your notification settings navigate to Profile Settings > Notifications > Global notification level and choose your preferences from the dropdown menu.

Tip: Avoid mentioning @all in issues and merge requests, as it sends an email notification to all the members of that project's group, which can be interpreted as spam.

15. Award emoji

Tip: Posting "+1" as comments in threads spam all participants of that issue. Awarding an emoji is a way to let them know you like it without spamming them.

16. Thread

17. Comment, start a discusion, or comment and close

Once you wrote your comment, you can either:

18. New Merge Request

Leave a comment below if you have any feedback on the documentation. For support and other inquires, see getting help.