Obsidian Gitlab Issues

by Ben Roberts
5
4
3
2
1
Score: 53/100

Description

Category: 3rd Party Integrations

The Obsidian Gitlab Issues plugin allows users to seamlessly integrate Gitlab issues into their Obsidian vault. This plugin fetches issues from Gitlab and generates individual read-only Obsidian notes for each issue in a designated output directory. It updates the issues automatically every 15 minutes, ensuring synchronization with the latest status from Gitlab. Users can customize the note format using Handlebars templates and adjust API query filters to suit their specific needs, such as filtering issues by due date. The plugin also supports integration with the Dataview Plugin for advanced issue tracking and visualization, enabling efficient project management within Obsidian.

Reviews

No reviews yet.

Stats

31
stars
5,484
downloads
23
forks
1,282
days
26
days
26
days
14
total PRs
1
open PRs
4
closed PRs
9
merged PRs
24
total issues
14
open issues
10
closed issues
5
commits

Latest Version

a month ago

Changelog

What's Changed

New Contributors

Full Changelog: https://github.com/benr77/obsidian-gitlab-issues/compare/0.1.10...0.1.11

README file from

Github

Gitlab Issues for Obsidian

CI Build Status Github All Releases

A plugin for Obsidian to import issues from Gitlab.

Each issue returned from Gitlab is created as an Obsidian note in the specified output directory.

You can create your own template to customise the format of the issue note.

Notes are intended to be READ ONLY, as they will be removed from your Obsidian vault if they no longer are returned by Gitlab.

The latest issues are loaded from Gitlab 30 seconds after Obsidian is started, and then automatically every 15 minutes.

Configuration

You must have a Gitlab account.

  1. Generate a Gitlab Personal Access Token for the plugin that has API scope included.
  2. Install the plugin through the Obsidian Community Plugins section, and then enable it.
  3. Enter the Personal Access Token you created at Gitlab into the Token field in the plugin settings.

Plugin Settings Screen

Example - Listing upcoming deadlines

With the default filter value of due_date=month, the Gitlab API will return all issues that have a Due Date in the next month.

The plugin will create an Obsidian note file for each issue.

You can then use the excellent DataView Plugin to create lists of upcoming issues to embed anywhere you like in your vault. For example:

dataview
TABLE WITHOUT ID file.link AS "Task", dueDate AS "Due Date" from "@Data/Gitlab Issues"
SORT dueDate

If you then close an issue on Gitlab, or change its due date to be further in the future, the issue will be removed from your vault, and the DataView list will no longer show the issue.

Going Further

Customise the API query

You can use any valid query filter permitted by Gitlab in the "Issues List" endpoint. See the Gitlab API Documentation for all possible options.

Use a custom template

You can customise the template used to create the new notes. Create a note for the template, and specify the path to this note in the plugin settings.

The template must be a valid Handlebars template. See the Handlebars documentation for more information on the syntax.

Currently, the available fields include:

id title description due_date web_url

Bugs

Please report bugs right here in the repository issues section.

Contributions

Contributions are welcome. Please submit a single PR per bug or feature.

License

The plugin code is released under the MIT license. See the LICENSE document for more information.

Similar Plugins

info
• Similar plugins are suggested based on the common tags between the plugins.