Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36,894
    • Issues 36,894
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,479
    • Merge requests 1,479
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Merge requests
  • !46161

Merged
Created Oct 26, 2020 by Nathan Friend@nfriend💡Maintainer

Add link paths for release progress view to GraphQL

  • Overview 16
  • Commits 2
  • Pipelines 5
  • Changes 11

What does this MR do?

Adds 5 new fields to the Release GraphQL type:

  • openMergeRequestsUrl
  • mergedMergeRequestsUrl
  • closedMergeRequestsUrl
  • openIssuesUrl
  • closedIssuesUrl

These URLs will be used to link the user from the release progress view to the issue and merge request search pages:

image

Currently the numbers render as plain text; once the frontend begins requesting these fields, the numbers will be rendered as links as shown in the screenshot above.

What doesn't this MR do?

This MR does not add these properties to the Release REST API. These links will be added in a separate MR.

Example query/response

Query:

{
  project(fullPath: "root/release-test") {
    release(tagName: "v5.10") {
      links {
        openIssuesUrl
        closedIssuesUrl
        openMergeRequestsUrl
        mergedMergeRequestsUrl
        closedMergeRequestsUrl
        
        # These fields are now deprecated
        issuesUrl
        mergeRequestsUrl
      }
    }
  }
}

Response:

{
  "data": {
    "project": {
      "release": {
        "links": {
          "openIssuesUrl": "http://0.0.0.0:3000/root/release-test/-/issues?release_tag=v5.10&scope=all&state=opened",
          "closedIssuesUrl": "http://0.0.0.0:3000/root/release-test/-/issues?release_tag=v5.10&scope=all&state=closed",
          "openMergeRequestsUrl": "http://0.0.0.0:3000/root/release-test/-/merge_requests?release_tag=v5.10&scope=all&state=opened",
          "mergedMergeRequestsUrl": "http://0.0.0.0:3000/root/release-test/-/merge_requests?release_tag=v5.10&scope=all&state=merged",
          "closedMergeRequestsUrl": "http://0.0.0.0:3000/root/release-test/-/merge_requests?release_tag=v5.10&scope=all&state=closed",
          "issuesUrl": "http://0.0.0.0:3000/root/release-test/-/issues?release_tag=v5.10&scope=all&state=opened",
          "mergeRequestsUrl": "http://0.0.0.0:3000/root/release-test/-/merge_requests?release_tag=v5.10&scope=all&state=opened"
        }
      }
    }
  }
}

Feature flag

These URLs are only available if the release_mr_issue_urls feature flag is enabled. This is an existing flag, so it is already defaulted to on.

Related to #205349 (closed)

Edited Oct 26, 2020 by Nathan Friend
Assignee
Assign to
Reviewer
Request review from
13.6
Milestone
13.6 (Past due)
Assign milestone
Time tracking
Source branch: nfriend-add-release-progress-link-paths