Open pnadolny13 opened 2 years ago
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)
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
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
In GitLab by @NicoleSchwartz on Dec 19, 2019, 12:35
In GitLab by @NicoleSchwartz on Dec 19, 2019, 12:35
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
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!
In GitLab by @DouweM on Dec 20, 2019, 05:12
unassigned @DouweM
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.
In GitLab by @derek-knox on Dec 19, 2019, 11:51
A user request:
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.