sincecutoff.com
← all changes

GitHub GraphQL API issue filters accept issue field values

Introduced 2026-08-12 · score 0.90

HOW TO USE IT

When maintaining issue triage by project field values, filter the repository’s issues with `IssueFilters.issueFieldValues` and provide exactly one field selector and one value filter per filter object.

query { repository(owner: "<owner>", name: "<repo>") { issues(first: 100, filterBy: { issueFieldValues: [{ fieldName: "<field-name>", textValue: "<text>" }] }) { nodes { id title } } } }

WHY THIS HELPS

Filter issues by values in their project fields when maintaining an issue-triage workflow.

REQUIREMENTS AND LIMITATIONS

  • filterBy: Issue connection filtering options.
  • issueFieldValues: List issues where each supplied issue field value filter matches.
  • fieldId: Issue field ID selector; provide exactly one of `fieldId` or `fieldName`.
  • fieldName: Issue field name selector; provide exactly one of `fieldName` or `fieldId`.
  • dateValue: Matches a date field value in `YYYY-MM-DD` format.
  • numberValue: Matches a numeric field value.
  • textValue: Matches a text field value.
  • singleSelectOptionId: Matches a single-select option by ID.
  • singleSelectOptionValue: Matches a single-select option by name.
  • multiSelectOptionIds: Matches issues containing all listed multi-select option IDs.
  • multiSelectOptionValues: Matches issues containing all listed multi-select option names.
  • IssueFieldValueFilter value argument (required): Exactly one of `dateValue`, `numberValue`, `textValue`, `singleSelectOptionId`, `singleSelectOptionValue`, `multiSelectOptionIds`, or `multiSelectOptionValues` should be provided.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card