Expose issuesSettings GraphQL field

What does this MR do and why?

As part of the configurable work item statuses work, the frontend needs access to the issues settings path where configurable lifecycles and statuses are defined and managed.

This MR adds the issuesSettings field to the namespacesLinkPaths GraphQL API to provide easy access to that path.

Notes

  • Configurable work item statuses are only available for groups and projects. issuesSettings returns nil for user namespaces, which are not yet supported.
  • issuesSettings always returns a path for root-level groups, since lifecycles and statuses are defined at the root and cascade down to subgroups and projects.

References

Screenshots or screen recordings

Namespace Screenshot
Root group namespace Screenshot_2025-07-25_at_6.57.02_pm
Subgroup namespace Screenshot_2025-07-25_at_7.20.09_pm
Project namespace Screenshot_2025-07-25_at_6.57.30_pm
User namespace Screenshot_2025-07-25_at_6.59.19_pm

How to set up and validate locally

  1. Run the following query for the group, project and user namespaces to test the new issuesSettings GraphQL field.
query namespaceLinkPaths {
  namespace(fullPath: "flightjs/Flight") {
    id
    fullPath
    linkPaths {
      issuesSettings
    }
  }
}

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.

Edited by Agnes Slota

Merge request reports

Loading