[go: up one dir, main page]

Skip to content

Draft: Expose hasStatusesFeature and adminWorkItemLifecycle GraphQL fields

What does this MR do and why?

Expose hasStatusesFeature and adminWorkItemLifecycle GraphQL fields.

References

Screenshots or screen recordings

hasStatusesFeature - group level Screenshot_2025-07-24_at_3.33.09_pm
hasStatusesFeature - project level Screenshot_2025-07-24_at_3.34.45_pm
adminWorkItemLifecycle Screenshot_2025-07-24_at_3.24.45_pm

How to set up and validate locally

  1. Run the following queries to test new GraphQL fields.
hasStatusesFeature

Group-level

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

Project-level

query availableFeatures {
  namespace(fullPath: "flightjs/Flight") {
    id
    availableFeatures {
      hasStatusesFeature
    }
  }
}
adminWorkItemLifecycle
query workspacePermissions {
  workspace: group(fullPath: "flightjs") {
    userPermissions {
      adminIssue
      adminWorkItemLifecycle
    }
  }
}

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