GLQL fields

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

With GitLab Query Language (GLQL), fields are used to:

Filter the results returned from a GLQL query.
Control the details displayed in an embedded view.
Sort the results displayed in an embedded view.

You use fields in three embedded view parameters:

query - Set conditions to determine which items to retrieve
fields - Specify which columns and details appear in your view
sort - Order items by specific criteria

The following sections describe the available fields for each component.

Fields inside query

In an embedded view, the query parameter can be used to include one or more expressions of the format <field> <operator> <value>. Multiple expressions are joined with and, for example, group = "gitlab-org" and author = currentUser().

Prerequisites:

Querying epics is available in the Premium and Ultimate tier.

The table below provides an overview of all available query fields and their specifications:

Field	Name (and alias)	Operators	Supported for
Approved by user	`approver`, `approvedBy`, `approvers`	`=`, `!=`	Merge requests
Assignees	`assignee`, `assignees`	`=`, `in`, `!=`	Issues, epics, merge requests
Author	`author`	`=`, `in`, `!=`	Issues, epics, merge requests
Cadence	`cadence`	`=`, `in`	Issues
Closed at	`closed`, `closedAt`	`=`, `>`, `<`, `>=`, `<=`	Issues, epics
Confidential	`confidential`	`=`, `!=`	Issues, epics
Created at	`created`, `createdAt`, `opened`, `openedAt`	`=`, `>`, `<`, `>=`, `<=`	Issues, epics, merge requests
Custom field	`customField("Field name")`	`=`	Issues, epics
Draft	`draft`	`=`, `!=`	Merge requests
Due date	`due`, `dueDate`	`=`, `>`, `<`, `>=`, `<=`	Issues, epics
Environment	`environment`	`=`	Merge requests
Epic	`epic`	`=`, `!=`	Issues
Group	`group`	`=`	Issues, epics, merge requests
Health status	`health`, `healthStatus`	`=`, `!=`	Issues, epics
ID	`id`	`=`, `in`	Issues, epics, merge requests
Include subgroups	`includeSubgroups`	`=`, `!=`	Issues, epics, merge requests
Iteration	`iteration`	`=`, `in`, `!=`	Issues
Labels	`label`, `labels`	`=`, `in`, `!=`	Issues, epics, merge requests
Merged at	`merged`, `mergedAt`	`=`, `>`, `<`, `>=`, `<=`	Merge requests
Merged by user	`merger`, `mergedBy`	`=`	Merge requests
Milestone	`milestone`	`=`, `in`, `!=`	Issues, epics, merge requests
My reaction emoji	`myReaction`, `myReactionEmoji`	`=`, `!=`	Issues, epics, merge requests
Project	`project`	`=`	Issues, merge requests
Reviewers	`reviewer`, `reviewers`, `reviewedBy`	`=`, `!=`	Merge requests
Source branch	`sourceBranch`	`=`, `in`, `!=`	Merge requests
State	`state`	`=`	Issues, epics, merge requests
Status	`status`	`=`	Issues
Subscribed	`subscribed`	`=`, `!=`	Issues, epics, merge requests
Target branch	`targetBranch`	`=`, `in`, `!=`	Merge requests
Type	`type`	`=`, `in`	Issues, epics, merge requests
Updated at	`updated`, `updatedAt`	`=`, `>`, `<`, `>=`, `<=`	Issues, epics, merge requests
Weight	`weight`	`=`, `!=`	Issues

Approved by user

Description: Query merge requests by one or more users who approved the merge request.

Allowed value types:

String
User (for example, @username)
List (containing String or User values)
Nullable (either of null, none, or any)

Examples:

List all merge requests approved by current user and @johndoe

type = MergeRequest and approver = (currentUser(), @johndoe)

List all merge requests that are not yet approved
```
type = MergeRequest and approver = none
```

Assignees

Description: Query issues, epics, or merge requests by one or more users who are assigned to them.

Allowed value types:

String
User (for example, @username)
List (containing String or User values)
Nullable (either of null, none, or any)

Additional details:

List values and the in operator are not supported for MergeRequest types.

Examples:

List all issues where assignee is @johndoe:
```
assignee = @johndoe
```
List all issues where assignees are both @johndoe and @janedoe:
```
assignee = (@johndoe, @janedoe)
```
List all issues where assignees are either of @johndoe or @janedoe:
```
assignee in (@johndoe, @janedoe)
```
List all issues where assignee is neither of @johndoe or @janedoe:
```
assignee != (@johndoe, @janedoe)
```
List all merge requests where assignee is @johndoe:
```
type = MergeRequest and assignee = @johndoe
```

Author

Description: Query issues, epics, or merge requests by their author.

Allowed value types:

String
User (for example, @username)
List (containing String or User values)

Additional details:

The in operator is not supported for MergeRequest types.

Examples:

List all issues where author is @johndoe:
```
author = @johndoe
```
List all epics where author is either @johndoe or @janedoe:
```
type = Epic and author in (@johndoe, @janedoe)
```
List all merge requests where author is @johndoe:
```
type = MergeRequest and author = @johndoe
```

Cadence

Description: Query issues by the cadence that the issue’s iteration is a part of.

Allowed value types:

Number (only positive integers)
List (containing Number values)
Nullable (either of none, or any)

Additional details:

Because an issue can have only one iteration, the = operator cannot be used with List type for the cadence field.

Examples:

List all issues with iteration that are a part of cadence ID 123456:
```
cadence = 123456
```
List all issues with iterations that are a part of any cadences 123 or 456:
```
cadence in (123, 456)
```

Closed at

Description: Query issues or epics by the date when they were closed.

Allowed value types:

AbsoluteDate (in the format YYYY-MM-DD)
RelativeDate (in the format <sign><digit><unit>, where sign is +, -, or omitted, digit is an integer, and unit is one of d (days), w (weeks), m (months) or y (years))

Additional details:

For the = operator, the time range is considered from 00:00 to 23:59 in the user’s time zone.
>= and <= operators are inclusive of the dates being queried, whereas > and < are not.

Examples:

List all issues closed since yesterday:
```
closed > -1d
```
List all issues closed today:
```
closed = today()
```
List all issues closed in the month of February 2023:
```
closed > 2023-02-01 and closed < 2023-02-28
```

Confidential

Description: Query issues or epics by their visibility to project members.

Allowed value types:

Boolean (either of true or false)

Additional details:

Confidential issues queried using GLQL are only visible to people who have permission to view them.

Examples:

List all confidential issues:
```
confidential = true
```
List all issues that are not confidential:
```
confidential = false
```

Created at

Description: Query issues, epics, or merge requests by the date when they were created.

Allowed value types:

AbsoluteDate (in the format YYYY-MM-DD)
RelativeDate (in the format <sign><digit><unit>, where sign is +, -, or omitted, digit is an integer, and unit is one of d (days), w (weeks), m (months) or y (years))

Additional details:

For the = operator, the time range is considered from 00:00 to 23:59 in the user’s time zone.
>= and <= operators are inclusive of the dates being queried, whereas > and < are not.

Examples:

List all issues that were created in the last week:
```
created > -1w
```
List all issues created today:
```
created = today()
```
List all issues created in the month of January 2025 that are still open:
```
created > 2025-01-01 and created < 2025-01-31 and state = opened
```

Custom field

Tier: Premium, Ultimate

Description: Query issues or epics by custom fields.

Allowed value types:

String (for single-select custom fields)
List (of String, for multi-select custom fields)

Additional details:

Custom field names and values are not case-sensitive.

Examples

List all issues where the single-select “Subscription” custom field is set to “Free”:
```
customField("Subscription") = "Free"
```
List all issues where the single-select “Subscription” and “Team” custom fields are set to “Free” and “Engineering” respectively:
```
customField("Subscription") = "Free" and customField("Team") = "Engineering"
```

List all issues where the multi-select “Category” custom field is set to “Markdown” and “Text Editors”:

customField("Category") = ("Markdown", "Text Editors")

Alternatively:

customField("Category") = "Markdown" and customField("Category") = "Text Editors"

Draft

Description: Query merge requests by their draft status.

Allowed value types:

Boolean (either of true or false)

Examples:

List all draft merge requests:
```
type = MergeRequest and draft = true
```
List all merge requests that are not in draft state:
```
type = MergeRequest and draft = false
```

Due date

Description: Query issues or epics by the date when they are due.

Allowed value types:

AbsoluteDate (in the format YYYY-MM-DD)
RelativeDate (in the format <sign><digit><unit>, where sign is +, -, or omitted, digit is an integer, and unit is one of d (days), w (weeks), m (months) or y (years))

Additional details:

For the = operator, the time range is considered from 00:00 to 23:59 in the user’s time zone.
>= and <= operators are inclusive of the dates being queried, whereas > and < are not.

Examples:

List all issues due in a week:
```
due < 1w
```
List all issues that were overdue as of January 1, 2025:
```
due < 2025-01-01
```
List all issues that are due today (but not due yesterday or tomorrow):
```
due = today()
```
List all issues that have been overdue in the last 1 month:
```
due > -1m and due < today()
```

Environment

Description: Query merge requests by the environment to which they have been deployed.

Allowed value types: String

Examples:

List all merge requests that have been deployed to environment production:
```
environment = "production"
```

Epic

Tier: Premium, Ultimate

Description: Query issues by their parent epic ID or reference.

Allowed value types:

Number (epic ID)
String (containing an epic reference like &123)
Epic (for example, &123, gitlab-org&123)

Examples:

List all issues that have epic &123 as their parent in project gitlab-org/gitlab:
```
project = "gitlab-org/gitlab" and epic = &123
```
List all issues that have epic gitlab-com&123 as their parent in project gitlab-org/gitlab:
```
project = "gitlab-org/gitlab" and epic = gitlab-com&123
```

Group

Description: Query issues, epics, or merge requests within all projects in a given group.

Allowed value types: String

Additional details:

Only one group can be queried at a time.
The group cannot be used together with the project field.
If omitted when using inside an embedded view in a group object (like an epic), group is assumed to be the current group.
Using the group field queries all objects in that group, all its subgroups, and child projects.
By default, issues or merge requests are searched in all descendant projects across all subgroups. To query only the direct child projects of the group, set the includeSubgroups field to false.

Examples:

List all issues in the gitlab-org group and any of its subgroups:
```
group = "gitlab-org"
```
List all Tasks in the gitlab-org group and any of its subgroups:
```
group = "gitlab-org" and type = Task
```

Health status

Tier: Ultimate

Description: Query issues or epics by their health status.

Allowed value types:

StringEnum (one of "needs attention", "at risk" or "on track")
Nullable (either of null, none, or any)

Examples:

List all issues that don’t have a health status set:
```
health = any
```
List all issues where the health status is “needs attention”:
```
health = "needs attention"
```

ID

Description: Query issues, epics, or merge requests by their IDs.

Allowed value types:

Number (only positive integers)
List (containing Number values)

Examples:

List issue with ID 123:
```
id = 123
```
List issues with IDs 1, 2, or 3:
```
id in (1, 2, 3)
```
List all merge requests with IDs 1, 2, or 3:
```
type = MergeRequest and id in (1, 2, 3)
```

Include subgroups

Description: Query issues, epics, or merge requests within the entire hierarchy of a group.

Allowed value types:

Boolean (either of true or false)

Additional details:

This field can only be used with the group field.
The value of this field defaults to false.

Examples:

List issues in any project that is a direct child of the gitlab-org group:
```
group = "gitlab-org" and includeSubgroups = false
```
List issues in any project within the entire hierarchy of the gitlab-org group:
```
group = "gitlab-org" and includeSubgroups = true
```

Iteration

Tier: Premium, Ultimate

Description: Query issues by their associated iteration.

Allowed value types:

Number (only positive integers)
Iteration (for example, *iteration:123456)
List (containing Number or Iteration values)
Enum (only current is supported)
Nullable (either of none, or any)

Additional details:

Because an issue can have only one iteration, the = operator cannot be used with List type for the iteration field.
The in operator is not supported for MergeRequest types.

Examples:

List all issues with iteration ID 123456 (using a number in the query):
```
iteration = 123456
```
List all issues that are a part of iterations 123 or 456 (using numbers):
```
iteration in (123, 456)
```
List all issues with iteration ID 123456 (using iteration syntax):
```
iteration = *iteration:123456
```
List all issues that are a part of iterations 123 or 456 (using iteration syntax):
```
iteration in (*iteration:123, *iteration:456)
```
List all issues in the current iteration
```
iteration = current
```

Labels

Description: Query issues, epics, or merge requests by their associated labels.

Allowed value types:

String
Label (for example, ~bug, ~"team::planning")
List (containing String or Label values)
Nullable (either of none, or any)

Additional details:

Scoped labels, or labels containing spaces must be wrapped in quotes.
The in operator is not supported for MergeRequest types.

Examples:

List all issues with label ~bug:
```
label = ~bug
```
List all issues not having label ~"workflow::in progress":
```
label != ~"workflow::in progress"
```
List all issues with labels ~bug and ~"team::planning":
```
label = (~bug, ~"team::planning")
```
List all issues with labels ~bug or ~feature:
```
label in (~bug, ~feature)
```
List all issues where the labels include neither of ~bug or ~feature:
```
label != (~bug, ~feature)
```
List all issues where none of the scoped labels apply, with scope workflow:::
```
label != ~"workflow::*"
```
List all merge requests with labels ~bug and ~"team::planning"
```
type = MergeRequest and label = (~bug, ~"team::planning")
```

Merged at

Description: Query merge requests by the date when they were merged.

Allowed value types:

AbsoluteDate (in the format YYYY-MM-DD)
RelativeDate (in the format <sign><digit><unit>, where sign is +, -, or omitted, digit is an integer, and unit is one of d (days), w (weeks), m (months) or y (years))

Additional details:

For the = operator, the time range is considered from 00:00 to 23:59 in the user’s time zone.
>= and <= operators are inclusive of the dates being queried, whereas > and < are not.

Examples:

List all merge requests that have been merged in the last 6 months:
```
type = MergeRequest and merged > -6m
```
List all merge requests that have been merged in the month of January 2025:
```
type = MergeRequest and merged > 2025-01-01 and merged < 2025-01-31
```

Merged by user

Description: Query merge requests by the user that merged the merge request.

Allowed value types:

String
User (for example, @username)

Examples:

List all merge requests merged by the current user:
```
type = MergeRequest and merger = currentUser()
```

Milestone

Description: Query issues, epics, or merge requests by their associated milestone.

Allowed value types:

String
Milestone (for example, %Backlog, %"Awaiting Further Demand")
List (containing String or Milestone values)
Nullable (either of none, or any)

Additional details:

Milestones containing spaces must be wrapped in quotes (").
Because an issue can have only one milestone, the = operator cannot be used with List type for the milestone field.
The in operator is not supported for MergeRequest and Epic types.
The Epic type does not support wildcard milestone filters like none or any.

Examples:

List all issues with milestone %Backlog:
```
milestone = %Backlog
```
List all issues with milestones %17.7 or %17.8:
```
milestone in (%17.7, %17.8)
```
List all issues in an upcoming milestone:
```
milestone = upcoming
```
List all issues in a current milestone:
```
milestone = started
```
List all issues where the milestone is neither of %17.7 or %17.8:
```
milestone != (%17.7, %17.8)
```

My reaction emoji

Description: Query issues, epics, or merge requests by the current user’s emoji reaction on it.

Allowed value types: String

Examples:

List all issues where the current user reacted with the thumbs-up emoji:
```
myReaction = "thumbsup"
```
List all merge requests where the current user did not react with the thumbs-down emoji:
```
type = MergeRequest and myReaction != "thumbsdown"
```

Project

Description: Query issues or merge requests within a particular project.

Allowed value types: String

Additional details:

Only one project can be queried at a time.
The project field cannot be used together with the group field.
If omitted when using inside an embedded view, project is assumed to be the current project.

Examples:

List all issues and work items in the gitlab-org/gitlab project:
```
project = "gitlab-org/gitlab"
```

Reviewers

Description: Query merge requests that were reviewed by one or more users.

Allowed value types:

String
User (for example, @username)
Nullable (either of null, none, or any)

Examples:

List all merge requests reviewed by current user:
```
type = MergeRequest and reviewer = currentUser()
```

Source branch

Description: Query merge requests by their source branch.

Allowed value types: String, List

Additional details:

List values are only supported with the in and != operators.

Examples:

List all merge requests from a specific branch:

type = MergeRequest and sourceBranch = "feature/new-feature"

List all merge requests from multiple branches:

type = MergeRequest and sourceBranch in ("main", "develop")

List all merge requests that are not from a specific branch:
```
type = MergeRequest and sourceBranch != "main"
```

State

Description: Query issues, epics, or merge requests by state.

Allowed value types:

Enum
- For issue and work item types, one of opened, closed, or all
- For MergeRequest types, one of opened, closed, merged, or all

Additional details:

The state field does not support the != operator.

Examples:

List all closed issues:
```
state = closed
```
List all open issues:
```
state = opened
```
List all issues regardless of their state (also the default):
```
state = all
```
List all merged merge requests:
```
type = MergeRequest and state = merged
```

Status

Tier: Premium, Ultimate

Description: Query issues by their status.

Allowed value types: String

Examples:

List all issues with status “To do”:
```
status = "To do"
```

Subscribed

Description: Query issues, epics, or merge requests by whether the current user has set notifications on or off.

Allowed value types: Boolean

Examples:

List all open issues where the current user has set notifications on:
```
state = opened and subscribed = true
```
List all merge requests where the current user has set notifications off:
```
type = MergeRequest and subscribed = false
```

Target branch

Description: Query merge requests by their target branch.

Allowed value types: String, List

Additional details:

List values are only supported with the in and != operators.

Examples:

List all merge requests targeting a specific branch:

type = MergeRequest and targetBranch = "feature/new-feature"

List all merge requests targeting multiple branches:

type = MergeRequest and targetBranch in ("main", "develop")

List all merge requests that are not targeting a specific branch:
```
type = MergeRequest and targetBranch != "main"
```

Type

Description: The type of object to query: issues, epics, or merge requests.

Allowed value types:

Enum, one of:
- Issue
- Incident
- Epic
- TestCase
- Requirement
- Task
- Ticket
- Objective
- KeyResult
- MergeRequest
List (containing one or more enum values)

Additional details:

If omitted when used inside an embedded view, the default type is Issue.
type = Epic queries can only be used together with the group field.
The in operator cannot be used to combine Epic and MergeRequest types with other types in the same query.

Examples:

List incidents:
```
type = incident
```
List issues and tasks:
```
type in (Issue, Task)
```
List all merge requests assigned to the current user:
```
type = MergeRequest and assignee = currentUser()
```
List all epics authored by the current user in the group gitlab-org
```
group = "gitlab-org" and type = Epic and author = currentUser()
```

Updated at

Description: Query issues, epics, or merge requests by when they were last updated.

Allowed value types:

AbsoluteDate (in the format YYYY-MM-DD)
RelativeDate (in the format <sign><digit><unit>, where sign is +, -, or omitted, digit is an integer, and unit is one of d (days), w (weeks), m (months) or y (years))

Additional details:

For the = operator, the time range is considered from 00:00 to 23:59 in the user’s time zone.
>= and <= operators are inclusive of the dates being queried, whereas > and < are not.

Examples:

List all issues that haven’t been edited in the last 1 month:
```
updated < -1m
```
List all issues that were edited today:
```
updated = today()
```
List all open MRs that haven’t been edited in the last 1 week:
```
type = MergeRequest and state = opened and updated < -1w
```

Weight

Tier: Premium, Ultimate

Description: Query issues by their weight.

Allowed value types:

Number (only positive integers or 0)
Nullable (either of null, none, or any)

Additional details:

Comparison operators < and > cannot be used.

Examples:

List all issues with weight 5:
```
weight = 5
```
List all issues with weight not 5:
```
weight != 5
```

Fields in embedded views

In embedded views, the fields view parameter is a comma-separated list of fields, or field functions that can be used to indicate what fields to include in the rendered embedded view, for example, fields: title, state, health, epic, milestone, weight, updated.

Field	Name or alias	Objects supported	Description
Approved by user	`approver`, `approvers`, `approvedBy`	Merge requests	Display users who approved the merge request
Assignees	`assignee`, `assignees`	Issues, merge requests	Display users assigned to the object
Author	`author`	Issues, epics, merge requests	Display the author of the object
Closed at	`closed`, `closedAt`	Issues, epics, merge requests	Display time since the object was closed
Confidential	`confidential`	Issues, epics	Display `Yes` or `No` indicating whether the object is confidential
Created at	`created`, `createdAt`	Issues, epics, merge requests	Display time since the object was created
Description	`description`	Issues, epics, merge requests	Display the description of the object
Draft	`draft`	Merge requests	Display `Yes` or `No` indicating whether the merge request is in draft state
Due date	`due`, `dueDate`	Issues, epics	Display time until the object is due
Epic	`epic`	Issues	Display a link to the epic for the issue. Available in the Premium and Ultimate tier
Health status	`health`, `healthStatus`	Issues, epics	Display a badge indicating the health status of the object. Available in the Ultimate tier
ID	`id`	Issues, epics, merge requests	Display the ID of the object
Iteration	`iteration`	Issues	Display the iteration associated with the object. Available in the Premium and Ultimate tier
Labels	`label`, `labels`	Issues, epics, merge requests	Display labels associated with the object. Can accept parameters to filter specific labels, for example `labels("workflow::*", "backend")`
Last comment	`lastComment`	Issues, epics, merge requests	Display the last comment made on the object
Merged at	`merged`, `mergedAt`	Merge requests	Display time since the merge request was merged
Milestone	`milestone`	Issues, epics, merge requests	Display the milestone associated with the object
Reviewers	`reviewer`, `reviewers`	Merge requests	Display users assigned to review the merge request
Source branch	`sourceBranch`	Merge requests	Display the source branch of the merge request
Source project	`sourceProject`	Merge requests	Display the source project of the merge request
Start date	`start`, `startDate`	Epics	Display the start date of the epic
State	`state`	Issues, epics, merge requests	Display a badge indicating the state of the object. For issues and epics, values are `Open` or `Closed`. For merge requests, values are `Open`, `Closed`, or `Merged`
Status	`status`	Issues	Display a badge indicating the status of the issue. For example, “To do” or “Complete”. Available in the Premium and Ultimate tiers.
Subscribed	`subscribed`	Issues, epics, merge requests	Display `Yes` or `No` indicating whether the current user is subscribed to the object or not
Target branch	`targetBranch`	Merge requests	Display the target branch of the merge request
Target project	`targetProject`	Merge requests	Display the target project of the merge request
Title	`title`	Issues, epics, merge requests	Display the title of the object
Type	`type`	Issues, epics	Display the work item type, for example `Issue`, `Task`, or `Objective`
Updated at	`updated`, `updatedAt`	Issues, epics, merge requests	Display time since the object was last updated
Weight	`weight`	Issues	Display the weight of the object. Available in the Premium and Ultimate tiers.

Fields to sort embedded views by

In embedded views, the sort view parameter is a field name followed by a sort order (asc or desc) that sorts the results by the specified field and order.

Field	Name (and alias)	Supported for	Description
Closed at	`closed`, `closedAt`	Issues, epics, merge requests	Sort by closed date
Created	`created`, `createdAt`	Issues, epics, merge requests	Sort by created date
Due date	`due`, `dueDate`	Issues, epics	Sort by due date
Health status	`health`, `healthStatus`	Issues, epics	Sort by health status
Merged at	`merged`, `mergedAt`	Merge requests	Sort by merge date
Milestone	`milestone`	Issues, merge requests	Sort by milestone due date
Popularity	`popularity`	Issues, epics, merge requests	Sort by the number of thumbs up emoji reactions
Start date	`start`, `startDate`	Epics	Sort by start date
Title	`title`	Issues, epics, merge requests	Sort by title
Updated at	`updated`, `updatedAt`	Issues, epics, merge requests	Sort by last updated date
Weight	`weight`	Issues	Sort by weight

Examples:

List all issues in the gitlab-org/gitlab project sorted by title. Display columns state, title, and updated.

```glql
display: table
fields: state, title, updated
sort: title asc
query: project = "gitlab-org/gitlab" and type = Issue
```

List all merge requests in the gitlab-org group assigned to the authenticated user sorted by the merge date (latest first). Display columns title, reviewer, and merged.

```glql
display: table
fields: title, reviewer, merged
sort: merged desc
query: group = "gitlab-org" and type = MergeRequest and state = merged and author = currentUser()
limit: 10
```

List all epics in the gitlab-org group sorted by the start date (oldest first). Display columns title, state, and startDate.

```glql
display: table
fields: title, state, startDate
sort: startDate asc
query: group = "gitlab-org" and type = Epic
```

List all issues in the gitlab-org group with an assigned weight sorted by the weight (highest first). Display columns title, weight, and health.
```
```glql
display: table
fields: title, weight, health
sort: weight desc
query: group = "gitlab-org" and weight = any
```
```
List all issues in the gitlab-org group due up to a week from today sorted by the due date (earliest first). Display columns title, duedate, and assignee.
```
```glql
display: table
fields: title, dueDate, assignee
sort: dueDate asc
query: group = "gitlab-org" and due >= today() and due <= 1w
```
```

Troubleshooting

Query timeout errors

You might encounter these error messages:

Embedded view timed out. Add more filters to reduce the number of results.

Query temporarily blocked due to repeated timeouts. Please try again later or try narrowing your search scope.

These errors occur when your query takes too long to execute. Large result sets and broad searches can cause timeouts.

To resolve this issue, add filters to limit your search scope:

Add time range filters to limit results to a specific period, by using date fields like created, updated, or closed. For example:

```glql
display: table
fields: title, labels, created
query: group = "gitlab-org" and label = "group::knowledge" and created > "2025-01-01" and created < "2025-03-01"
```

Filter by recent updates to focus on active items:

```glql
display: table
fields: title, labels, updated
query: group = "gitlab-org" and label = "group::knowledge" and updated > -3m
```

Use project-specific queries instead of group-wide searches when possible:

```glql
display: table
fields: title, state, assignee
query: project = "gitlab-org/gitlab" and state = opened and updated > -1m
```