Add STATUS_ASC and STATUS_DESC to WorkItemSort enum
What does this MR do and why?
This MR adds STATUS_ASC and STATUS_DESC sorting options to the WorkItemSort enum. These options will later be used to sort work items by status in ascending or descending order.
Since the sorting implementation is complex and unlikely to be deployed before the 18.3 cut-off, this MR only exposes the sorting options in GraphQL. In a follow-up MR, we'll introduce the sorting functionality along with the required scopes.
When STATUS_ASC or STATUS_DESC is provided in the GraphQL query, results are returned as-is, without any sorting applied.
Notes
We won't be exposing the sorting functionality in the legacy issue lists, meaning STATUS_ASC and STATUS_DESC will only be exposed in the Work Items API.
References
Screenshots or screen recordings
| STATUS_ASC | STATUS_DESC |
|---|---|
![]() |
![]() |
How to set up and validate locally
- Run the following queries to test the
STATUS_ASCandSTATUS_DESCsorting options. Since the sorting functionality will be implemented later, the results are returned as-is, without any sorting applied.
query {
project(fullPath: "flightjs/Flight") {
workItems(
sort: STATUS_ASC
) {
edges {
node {
id
title
widgets {
type
... on WorkItemWidgetStatus {
status {
name
category
}
}
}
}
}
}
}
}
query {
project(fullPath: "flightjs/Flight") {
workItems(
sort: STATUS_DESC
) {
edges {
node {
id
title
widgets {
type
... on WorkItemWidgetStatus {
status {
name
category
}
}
}
}
}
}
}
}
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.

