- Access the To-Do List
- Search the To-Do List
- Actions that create to-do items
- Create a to-do item
- Create a to-do item by mentioning someone
- Actions that mark a to-do item as done
- Mark a to-do item as done
- Mark all to-do items as done
- How a user’s To-Do List is affected when their access changes
Your To-Do List is a chronological list of items waiting for your input. The items are known as to-do items.
You can use the To-Do List to track actions related to:
To access your To-Do List:
On the top bar, in the upper right, select To-Do List ().
You can search your To-Do List by
to do and
You can filter to-do items per project, author, type, and action. Also, you can sort them by Label priority, Last created, and Oldest created.
Many to-do items are created automatically. A to-do item is added to your To-Do List when:
- An issue or merge request is assigned to you.
- You’re mentioned in the description or comment of an issue, merge request, or epic.
- You are mentioned in a comment on a commit or design.
- The CI/CD pipeline for your merge request fails.
- An open merge request cannot be merged due to conflict, and one of the
following is true:
- You’re the author.
- You’re the user that set the merge request to automatically merge after a pipeline succeeds.
- In GitLab 13.2 and later, a merge request is removed from a merge train, and you’re the user that added it.
- In GitLab 15.8 and later, a member access request is raised for a group or project you’re an owner of.
When several actions occur for the same user on the same object, GitLab displays the first action as a single to-do item. To change this behavior, enable multiple to-do items per object.
To-do items aren’t affected by GitLab notification email settings.
multiple_todos. On GitLab.com, this feature is not available. The feature is not ready for production use.
When you enable this feature:
- Every time you’re mentioned, GitLab creates a new to-do item for you.
- Other actions that create to-do items create one to-do item per action type on the issue, MR, and so on.
You can manually add an item to your To-Do List.
Go to your:
On the right sidebar, at the top, select Add a to do.
You can create a to-do item by mentioning someone anywhere except for a code block. Mentioning a user many times in one message only creates one to-do item.
For example, from the following comment, everyone except
frank gets a to-do item created for them:
@alice What do you think? cc: @bob - @carol can you please have a look? > @dan what do you think? Hey @erin, this is what they said: ``` Hi, please message @frank :incoming_envelope: ```
Various actions on the to-do item object (like issue, merge request, or epic) mark its corresponding to-do item as done.
To-do items are marked as done if you:
- Add an award emoji to the description or comment.
- Add or remove a label.
- Change the assignee.
- Change the milestone.
- Close the to-do item’s object.
- Create a comment.
- Edit the description.
- Resolve a design discussion thread.
- Accept or deny a project or group membership request.
To-do items are not marked as done if you:
- Add a linked item (like a linked issue).
- Add a child item (like child epic or task).
- Add a time entry.
- Assign yourself.
- Change the health status.
If someone else closes, merges, or takes action on an issue, merge request, or epic, your to-do item remains pending.
You can manually mark a to-do item as done.
There are two ways to do this:
- In the To-Do List, to the right of the to-do item, select Mark as done ().
In the sidebar of an issue, merge request, or epic, select Mark as done.
You can mark all your to-do items as done at the same time.
In the To-Do List, in the upper right, select Mark all as done.
For security reasons, GitLab deletes to-do items when a user no longer has access to a related resource. For example, if the user no longer has access to an issue, merge request, epic, project, or group, GitLab deletes the related to-do items.
This process occurs in the hour after their access changes. Deletion is delayed to prevent data loss, in case the user’s access was accidentally revoked.