Expose hasStatusesFeature GraphQL field

Agnes Slotarequested to merge
198863/aslota-expose-has-statuses-feature-field into master

What does this MR do and why?

Expose hasStatusesFeature field in the availableFeatures GraphQL API.

This allows the frontend to check for the work_item_status licensed feature directly via GraphQL, instead of injecting the check through HAML templates.

References

Screenshots or screen recordings
Group level Screenshot_2025-07-24_at_3.33.09_pm
Project level Screenshot_2025-07-24_at_3.34.45_pm

How to set up and validate locally

  1. Run the following queries at the group and project level to test the new hasStatusesFeature GraphQL field.

Group-level

query availableFeatures {
  namespace(fullPath: "flightjs") {
    id
    availableFeatures {
      hasStatusesFeature
    }
  }
}

Project-level

query availableFeatures {
  namespace(fullPath: "flightjs/Flight") {
    id
    availableFeatures {
      hasStatusesFeature
    }
  }
}

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.

Merge request reports