Jasper Handbook
jasperapp.io
English
English
  • What is Jasper
  • Quick start
    • Setup
    • Basic usage
    • Data migration
  • Use cases
    • Stream queries
    • Browse issues
    • Search issues
    • Appearance and notifications
    • Keyboard operation
    • Advanced settings
  • Reference
    • Stream
    • Filter Stream
    • Project Stream
    • Library Stream
    • System Stream
    • Sort order
    • Browser
    • Jump Navigation
    • Keyboard shortcuts
  • FAQ
  • jasperapp.io
  • jasperapp/jasper (GitHub)
Powered by GitBook
On this page
  • State of issues
  • Involve users and teams
  • Pull requests review
  • Repository and Organization
  • Label, milestone, etc
  • GitHub Project
  • Any keywords
  • Exclusion and missing

Was this helpful?

  1. Reference

Filter Stream

This is a reference for the filters available in Filter Stream.

PreviousStreamNextProject Stream

Last updated 2 years ago

Was this helpful?

Filter Stream filters the Stream's issues and displays them.

Filter Streams are added from the Add Filter Stream menu in the Stream menu. Or, to create a top-level stream, add it from the Add Filter Stream top-level menu. It is also possible to apply a Filter temporarily.

The filters available in the Filter Stream are pretty much the same as in the Stream, but note that some of them are slightly different.

State of issues

Filter
description

is:issue, is:pr

Issues only, pull requests only

is:open, is:closed

Opened issues, closed issues

is:merged, is:unmerged

Merged issues, unmerged issues

draft:true, draft:false

Draft issues, not draft issue‌s

is:read, is:unread

Read issues, unread issues

is:bookmark, is:unbookmark

Bookmarked issues, not bookmarked issue

is:archived, is:unarchived

Archived issues, not archived issues

is:private, is:unprivate

Private repository issues, not private repository issues

Involve users and teams

Filter
description

involves:defunkt

User involved issues

author:defunkt

User created issues

assignee:defunkt

User assigned issues

mentions:defunkt

User mentioned issues

team:github/owners

Team mentioned issues

Multiple filters of the same type can be specified as OR conditions. For example, involves:defunkt involves:jlord is issues involving defunkt or jlord.

involves as well as author, assignee, mentions,commenter and review-requested all together.‌

Pull requests review

Filter
description

review-requested:defunkt

Pull requests where the user/team has requested a review

reviewed-by:defunkt

User reviewed pull requests

Specifying multiple queries of the same type is an OR condition. For example, review-requested:defunkt review-requested:jlord is pull requests where defunkt or jlord is the review request.

Repository and Organization

Filter
description

repo:nodejs/node

Repository issues

org:nodejs

Organization issues

user:defunkt

User issues

Specifying multiple queries of the same type is an OR condition. For example, repo:nodejs/node repo:electron/electron is issues of nodejs/node or electron/electron.

Label, milestone, etc

Filter
description

label:bug, label:bug-%

Labeled issues % matches any string

milestone:v1.0.0, milestone:v2.0.%

Milestone issues % matches any string

title:test, title:%test%

Issue with specified title % matches any string

number:123

Issue number

Labels can also specify dynamic dates as follows.

Filter
Description (assuming today is 2022-08-16)

label:release_@current_date

@current_date is replaced by the current date. In other words, label:release_2022%08%16 is executed as a filter.

label:release_@prev_date

The @prev_date is replaced by yesterday's date. In other words, label:release_2022%08%15 is executed as a filter.

label:release_@next_date

The @next_date is replaced by tomorrow's date. In other words, label:release_2022%08%17 is executed as a filter.

label:release_@current_date+1, label:release_@current_date-1

Following @current_date with +1 or -1 replaces the date relative to the current date. So the filter will run label:release_2022%08%17 or label:release_2022%08%15.

Specifying multiple queries of the same type is an OR condition. For example, milestone:v1.0.0.0 milestone:v2.0.0 is issues with a v1.0.0 or v2.0.0.0 milestone. However, this is an AND condition for labels.

A label or milestone containing spaces should be enclosed in double quotation marks, such as label: "hello world".

GitHub Project

Filter
description

project-field:status/ToDo

Issue whose status field is ToDo

project-field:sprint/@current_iteration

Issue whose sprint field is the current iteration.

project-field:foo/bar

Issue where the foo field is bar

Below are the filters for the classic project.

Filter
description

project-name:hello-pj (classic project)

Issues tied to the project

project-column:now-doing (classic project)

Issue tied to project column

Any keywords

Filter
description

github octocat

Issues containing the keywords (AND conditions)

To include spaces, use double quotation marks, such as "hello world".

Search keywords in issue body, author, assignee, label, milestone, repository, org, involves, review-requested, review, project-name and project-columns.

OR and NOT are not supported.

Exclusion and missing

Filter
Condition

-label:bug, -milestone:v0.0.1, -repo:nodejs/node , -involves:defunk ,

and more

Issues that do not contain the specified conditions

no:label, no:milestone, no:assignee, no:project, no:dueon

Labels, Milestones, Assignments,

and An issue with no project set up

have:label, have:milestone, have:assignee, have:project, have:dueon

Labels, Milestones, Assignments,

and An issue with project set up