Stream queries

Stream allows you to specify flexible queries. Here are some of the most commonly used queries.

Open issues

You can use is:open to create a Stream to view issues in an open (unclosed or unmerged) state. For example, to view an open issue in the nodejs/node repository, you can create a Stream with the following query

repo:nodejs/node is:open is:issue

However, Jasper does not recommend using is:open to create a Stream because Jasper will not be able to detect when the Stream is closed from open to closed.

circle-info

This is a limitation of Jasper's polling of the GitHub Search API

So when using is:open, you should use the Filter Stream instead of the regular Stream. Filter Stream can be used to apply custom filters to a normal Stream. In the previous example, this would look like

Stream

repo:nodejs/node is:issue

Filter Stream

is:open
circle-info

For more information about Filter Stream, see "Filter Stream" in the reference.

circle-info

The same restrictions apply to close, merge and draft states.

Team mentioned issues

To view Team mentioned issues, use team:ORGNAME/TEAMNAME. For example, to view issues where @jekyll/owners are mentioned, create a Stream with a query like this

GitHub Docs: Search by team mentionarrow-up-right

User involved issues

To view issues involving a particular user, use the involves:USERNAME. For example, to see the issues involving a defunkt or jlord, create a Stream with a query like this

circle-info

The involves:USERNAME is a useful query to specify author, assign, mention, comment, and review-requested all together.

GitHub Docs: Search by a user that's involved in an issue or pull requestarrow-up-right

Repository and organization issues

To view issues in a specific repository, use repo:USERNAME/REPOSITORY. For example, to view issues in the nodejs/node or electron/electron repositories, you would create a Stream with a query like this

To view a specific Organization issue, use org:ORGNAME. For example, to view issues of the nodejs or electron Organization, you can create a Stream with a query like this

GitHub Docs: Search within a user's or organization's repositoriesarrow-up-right

Issues with milestones and labels

You can view issues with a specific milestone by using milestone:MILESTONE_NAME. For example, to see an issue with a milestone of 13.0.0 or 14.0.0 in the nodejs/node repository, create a Stream with a query like this

You can view issues labeled with a specific label using label:LABEL_NAME. For example, to view an issue labeled build and zlib in the nodejs/node repository, create a Stream with the following query

circle-info

If multiple labels are specified, it is an and condition.

circle-info

For milestones and labels that contain spaces, specify them as milestone: "foo bar".

GitHub Docs: Search by milestonearrow-up-right, Search by labelarrow-up-right

Issues containing the keywords

To view issues containing specific keywords, use the KEYWORD. For example, to see issues containing the octocat and github, create a Stream with the following query

circle-info

Keywords including multi-byte characters and spaces should be specified as "foo bar".

GitHub Docs: Limitations on query lengtharrow-up-right, Exclude certain resultsarrow-up-right

Exclusionary specification

You can use -QUALIFIER to exclude a specific repository, label or etc . For example, to view issues in the nodejs organizaton that do not contain a nodejs/node repository and a bug label, you can create a Stream with a query like this

GitHub Docs: Exclude certain resultsarrow-up-right

Last updated