You can import tasks from your Gitlab instance using the gitlab service name.

Example Service

Here’s an example of a Gitlab target:

service = gitlab
gitlab.login = ralphbean
gitlab.token = OMG_LULZ =

The above example is the minimum required to import issues from Gitlab. You can also feel free to use any of the configuration options described in Common Service Configuration Options or described in Service Features below.

The gitlab.token is your private API token.

Service Features

Include and Exclude Certain Repositories

If you happen to be working with a large number of projects, you may want to pull issues from only a subset of your repositories. To do that, you can use the gitlab.include_repos option.

For example, if you would like to only pull-in issues from your own project_foo and team bar‘s project_fox repositories, you could add this line to your service configuration (replacing me by your own login):

gitlab.include_repos = me/project_foo, bar/project_fox

Alternatively, if you have a particularly noisy repository, you can instead choose to import all issues excepting it using the gitlab.exclude_repos configuration option.

In this example, noisy/repository is the repository you would not like issues created for:

gitlab.exclude_repos = noisy/repository


If you omit the repository’s namespace, bugwarrior will automatically add your login as namespace. E.g. the following are equivalent:

gitlab.login = foo
gitlab.include_repos = bar


gitlab.login = foo
gitlab.include_repos = foo/bar

Import Labels as Tags

The gitlab issue tracker allows you to attach labels to issues; to use those labels as tags, you can use the gitlab.import_labels_as_tags option:

gitlab.import_labels_as_tags = True

Also, if you would like to control how these labels are created, you can specify a template used for converting the gitlab label into a Taskwarrior tag.

For example, to prefix all incoming labels with the string ‘gitlab‘ (perhaps to differentiate them from any existing tags you might have), you could add the following configuration option:

gitlab.label_template = gitlab_{{label}}

In addition to the context variable {{label}}, you also have access to all fields on the Taskwarrior task if needed.


See Field Templates for more details regarding how templates are processed.

Include Merge Requests

Although you can filter issues using Common Service Configuration Options, merge requests are not filtered by default. You can filter merge requests by adding the following configuration option:

gitlab.filter_merge_requests = True

Include Todo Items

By default todo items are not included. You may include them by adding the following configuration option:

gitlab.include_todos = True

If todo items are included, by default, todo items for all projects are included. To only fetch todo items for projects which are being fetched, you may set:

gitlab.include_all_todos = False

Include Only One Author

If you would like to only pull issues and MRs that you’ve authored, you may set:

gitlab.only_if_author = myusername


If your Gitlab instance is only available over HTTP, set:

gitlab.use_https = False

Do Not Verify SSL Certificate

If you want to ignore verifying the SSL certificate, set:

gitlab.verify_ssl = False

Provided UDA Fields

Field Name Description Type
gitlabdescription Description Text (string)
gitlabcreatedon Created Date & Time
gitlabmilestone Milestone Text (string)
gitlabnumber Issue/MR # Numeric
gitlabtitle Title Text (string)
gitlabtype Type Text (string)
gitlabupdatedat Updated Date & Time
gitlabduedate Due Date Date
gitlaburl URL Text (string)
gitlabrepo username/reponame Text (string)
gitlabupvotes Number of upvotes Numeric
gitlabdownvotes Number of downvotes Numeric
gitlabwip Work-in-Progress flag Numeric
gitlabauthor Issue/MR author Text (string)
gitlabassignee Issue/MR assignee Text (string)