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 queryis:open
to create a Stream because Jasper will not be able to detect when the Stream is closed from open to closed.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 liketeam:ORGNAME/TEAMNAME
. For example, to view issues where @jekyll/owners
are mentioned, create a Stream with a query like thisinvolves:USERNAME
. For example, to see the issues involving a defunkt
or jlord
, create a Stream with a query like thisinvolves:USERNAME
is a useful query to specify author, assign, mention, comment, and review-requested all together.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 thisorg:ORGNAME
. For example, to view issues of the nodejs
or electron
Organization, you can create a Stream with a query like thismilestone: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 thislabel:LABEL_NAME
. For example, to view an issue labeled build
and zlib
in the nodejs/node
repository, create a Stream with the following querymilestone: "foo bar"
.KEYWORD
. For example, to see issues containing the octocat
and github
, create a Stream with the following query"foo bar"
.-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