Add releases_path and project_import_jira_path to GraphQL

Vedant Jainrequested to merge
561205-migrate-work-items-data-from-haml-to-graphql-for-dynamic-contexts into master

What does this MR do and why?

Add releases_path and project_import_jira_path to GraphQL

Adds two new GraphQL fields to ProjectNamespaceLinksType:

  • releases_path: Project releases path
  • project_import_jira_path: JIRA import path

References

Relates to #561205 (closed)

Example Query

Query Result 
fragment namespaceURLs on Namespace {
    linkPaths {
      epicsList 
      ... on ProjectNamespaceLinks {
        releasesPath
        projectImportJiraPath
      }
    }
}

query getNamespaceLinks {
  public_project_namespace: namespace(fullPath: "twitter/Typeahead.Js") {
    ...namespaceURLs
  }
  public_group_namespace: namespace(fullPath: "twitter") {
    ...namespaceURLs
  }
}

{
  "data": {
    "public_project_namespace": {
      "linkPaths": {
        "epicsList": "/groups/twitter/-/epics",
        "releasesPath": "/twitter/Typeahead.Js/-/releases",
        "projectImportJiraPath": "/twitter/Typeahead.Js/-/import/jira"
      }
    },
    "public_group_namespace": {
      "linkPaths": {
        "epicsList": "/groups/twitter/-/epics"
      }
    }
  },
  "correlationId": "01K2HBATZBB0SX59CVPZQ5P493"
}

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #561205 (closed)

Merge request reports