get also linked issues for each issue in the obsidian text file

[gpuartifact]

Hi and Thanks for creating this plugin!

In Gitlab issues can be linked together.
To reflect this connection in obsidian with your plugin it would be great to include the linked issues using their respective names/file names (and id to get uniqueness) inside the text file with the [[]] brackets. That way also the graph would reflect this connectivity.

Guess the starting point would be https://docs.gitlab.com/ee/api/issue_links.html
, run search per issue and include an array with the linked_issues in the issue structure.

Plugins like yours really help making obsidian even more appealing to teams using gitlab. Thanks.

[benr77]

I'm not against the idea per-se, but I have some concerns.

1. This will require an API call for each issue that is returned. Currently we return all issues that match the filter using a single HTTP request. Implementing this would be 1+n HTTP requests, which for anything above a few issues could get pretty messy. Remember we query Gitlab on a regular basis to get the latest issue list.

2. I'm not convinced this should be part of the scope of the plugin. The basic idea of the plugin is simply to provide a synchronised list of issues inside Obsidian, and not to replicate what's going on in Gitlab. Currently you can access linked issues simply by clicking the link in your DataView table and going straight to Gitlab itself to look.

[gpuartifact]

regarding:

1. I do agree that this could be causing quite some traffic at first. But regarding updates, I wonder if this could be avoided if you only pull changes with filtering for date and time for changes since last request. And only update all if manually requested.

2. I think this could be added as an option. The interconnectivity of the issuess actually makes it more transparent and shows the dependencies. For e.g. if a fix to an issues involves various software subsystems, then this information is appreciated when you view the issue in obsidian.

I do understand your concern that this could be out of scope, basically replicating gitlab. But if I could vote I would vote for it ;-)