Extract Related Issues data

[pnadolny13]

In GitLab by @derek-knox on Dec 19, 2019, 11:51

A user request:

"Related issues" is there a plan to pull that in for the issues? if not i'd like to request it use case - i want to be able to see which of my issues are blocking the most other issues (i.e. highest value to knock out)

From what I could tell (via PGAdmin) we don't pull this data in. Related to the user request, we'd need to update the Models to ensure the UI can leverage it.

[pnadolny13]

In GitLab by @derek-knox on Dec 19, 2019, 11:52

cc @iroussos Putting this on your radar as I have a hunch this will be really simple to add (though I could be very wrong)

[pnadolny13]

In GitLab by @DouweM on Dec 19, 2019, 12:04

This depends on Related Issues information being available on the GitLab API, which unfortunately doesn't seem to be the case: https://docs.gitlab.com/ee/api/issues.html

[pnadolny13]

In GitLab by @NicoleSchwartz on Dec 19, 2019, 12:23

hrmf, ok well when "blocking issues" comes out i wonder if that would be a) better and b) in the api

[pnadolny13]

In GitLab by @NicoleSchwartz on Dec 19, 2019, 12:35

https://gitlab.com/gitlab-org/gitlab/issues/2035

[pnadolny13]

In GitLab by @NicoleSchwartz on Dec 19, 2019, 12:35

https://gitlab.com/gitlab-org/gitlab/issues/39058

[pnadolny13]

In GitLab by @NicoleSchwartz on Dec 19, 2019, 12:36

so 39058 may be a pre-req for this to actually be best for my sue case

[pnadolny13]

In GitLab by @DouweM on Dec 20, 2019, 05:11

@NicoleSchwartz tap-gitlab uses the REST API, so https://gitlab.com/gitlab-org/gitlab/merge_requests/21375 should do it!

[pnadolny13]

In GitLab by @DouweM on Dec 20, 2019, 05:12

unassigned @DouweM

[pnadolny13]

In GitLab by @cdownard on Apr 15, 2021, 19:35

Just thought I'd bump this as it is available on the GitLab API beginning a year ago. But the list view of issues doesn't pull back the issue links by default it appears. Seems it is a separate call to the :iid/issue_links end point.