Expose adminWorkItemLifecycle GraphQL field
What does this MR do and why?
Expose adminWorkItemLifecycle field in the group and project userPermissions GraphQL API.
This allows the frontend to check for the permission via GraphQL, instead of injecting the check through HAML templates.
As discussed here, this MR also updates the admin_work_item_lifecycle permission to ensure that only maintainers of a root group can administer work item lifecycles and their statuses. This is necessary because configurable work item lifecycles and statuses are defined at the root group level and cascade down to all subgroups and projects.
Notes
- The
adminWorkItemLifecyclefield will be used by the frontend to determine whether the current user has maintainer access to the root group. If the check passes, the status widget will display a link to the settings page where configurable lifecycles and statuses can be managed. Here's the related issue and designs.
References
Screenshots or screen recordings
| Group level - root maintainer | ![]() |
| Group level - guest | ![]() |
| Project level - root maintainer | ![]() |
| Project level - guest | ![]() |
| Project - personal | ![]() |
How to set up and validate locally
- Run the following queries at both the group and project levels using users with maintainer and non-maintainer roles.
- The
adminWorkItemLifecyclefield should returntrueonly when the user has maintainer access to the root group. - Additionally, navigate to the root group issues settings page (
/groups/flightjs/-/settings/issues) and verify that a root group maintainer can view and edit all configurable statuses.
Group-level
query workspacePermissions {
workspace: group(fullPath: "flightjs") {
userPermissions {
adminWorkItemLifecycle
}
}
}
Project-level
query workspacePermissions {
workspace: project(fullPath: "flightjs/Flight") {
userPermissions {
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




