feat: list the services a row's Jira issues link to - #5
Merged
Merged
Conversation
For every Jira issue found, collect reads its remote links
(GET /rest/api/2/issue/{key}/remotelink), keeps those pointing to a merge request
or commit on the configured GitLab endpoint, and stores them on the issue. The
page gains a Related services column: the other projects the row's issues link
to. A failed link lookup is recorded as the Jira error and exits 1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second step of the Jira phase: related services per row, from the issues' remote links.
What changes
collectreadsGET /rest/api/2/issue/{key}/remotelinkand keeps links to a merge request or commit onRELEASE_SCOPE_GITLAB__ENDPOINT. They are stored on the issue aslinks(kind, project, project URL, URL, iid or sha), deduplicated by URL.jira.error, and makescollectexit1; summaries and statuses already read are kept.schema_versionstays 2: 0.3.0 is not released yet and the field is additive.Design notes
relationship: mentioned on,object.url= MR or commit URL) but adds a comment only when comments are enabled, and the link needs no text parsing.Next
The
--jira KEYmode (repeatable): report only the services an issue links to, cut at its latest linked change, with the tag to release. Per-project cache pruning lands with it.