Skip to content

Commit 3d8e47d

Browse files
Update filtering-and-searching-issues-and-pull-requests.md (#55275)
Co-authored-by: Sarita Iyer <[email protected]>
1 parent 02a2474 commit 3d8e47d

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

content/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -77,10 +77,10 @@ You can build advanced filters using boolean and nested queries on your reposito
7777

7878
You can use `AND` and `OR` operators to refine your filters.
7979

80-
Use `AND` when you need results where both statements are true. In the example filter below, the results will be comprised of issues with the "Bug fix" label that are assigned to the @octocat user.
80+
Use `AND` when you need results where both statements are true. In the example filter below, the results will be comprised of issues with the "question" label that are assigned to the @octocat user.
8181

8282
```text
83-
label:"Bug fix" AND assignee:octocat
83+
label:"question" AND assignee:octocat
8484
```
8585

8686
To return results where either statement is true, use `OR`. In the example below, the results will contain issues assigned to either @octocat or @hubot.
@@ -93,10 +93,10 @@ If you choose not to use `AND` and `OR` operators, {% data variables.product.git
9393

9494
### Using parentheses for more complicated filters
9595

96-
You can also use parentheses to nest filters and group qualifiers. In the example below, the results will contain issues that are either assigned to @octocat with the "bug" issue type or assigned to @hubot with the "Enhancement" issue type.
96+
You can also use parentheses to nest filters and group qualifiers. In the example below, the results will contain issues that are either assigned to @octocat with the "bug" issue type or assigned to @hubot with the "Feature" issue type.
9797

9898
```text
99-
(type:"Bug" AND assignee:octocat) OR (type:"Enhancement" AND assignee:hubot)
99+
(type:"Bug" AND assignee:octocat) OR (type:"Feature" AND assignee:hubot)
100100
```
101101

102102
You can nest filters using parentheses up to five levels deep.{% ifversion ghes < 3.18 %} It's not currently possible to include the `repo`, `org`, or `user` qualifiers within parentheses.{% endif %}
@@ -224,7 +224,8 @@ For issues, you can also use search to:
224224

225225
* Filter for issues that are linked to a pull request by a closing reference: `linked:pr`
226226
* Filter issues by the reason they were closed: `is:closed reason:completed` or `is:closed reason:"not planned"`
227-
{% ifversion issue-types %}* Filter for issues with a particular type: `is:open type:"Bug"`{% endif %}
227+
{% ifversion issue-types %}* Filter for issues with a particular type: `is:open type:"Bug"`{% endif %}{% ifversion issues-advanced-search %}
228+
* Filter for issues from repositories [**owned**](/search-github/searching-on-github/searching-issues-and-pull-requests#search-within-a-users-or-organizations-repositories) by a certain user or organization, limited to up to 16 `user` and `org` qualifiers with no limit on `repo` qualifiers: `state:open type:issue org:github OR user:octocat`{% endif %}
228229

229230
For pull requests, you can also use search to:
230231

0 commit comments

Comments
 (0)